TEXAS · WELLS · MONTAGUE COUNTY · YARBROUGH LEASE · API 42-337-32816 · DISTRICT 7C

Yarbrough #1

Plugged

Montague County · Dyemound S. (Bend Conglomerate) field  · Vertical

Yarbrough #1 (API 42-337-32816) is a plugged well in Montague County, plugged April 12, 2016, last operated by Walsh & Watts Inc..

The RRC has issued one drilling permit, issued November 10, 1989, permitted to 7,300 ft.

It was permitted by Fortson Oil Company and has since transferred to Walsh & Watts Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Etter, Caddo.

Its lease has reported 85.1K barrels of oil and 106K mcf of gas since January 1993, last reporting in May 2016.

Operator of record

Walsh & Watts Inc.

Permitted by Fortson Oil Company; the EWA schedule now lists a different operator.

Based in
Aledo, TX
P-5 status
Active (A)
P-5 last filed
Dec 2, 2025
Permits on file
361
Phone
(469) 428-3381

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWalsh & Watts Inc.
Production reportsWalsh & Watts, Inc.through Nov 2015
Latest permitFortson Oil CompanyNov 10, 1989

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

7,300
total depth, ft
1
permits on file
Nov 10, 1989
last permit issued
Jan 10, 1990
completed
85.1K
cumulative oil, bbl
106K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 10, 1990
Shut in
—
Plugged
Apr 12, 2016

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Yarbrough O-13-27620Dyemound, S. (Bend Conglomerate)Walsh & Watts, Inc.185.1K106KJan 1993 – May 2016

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Fortson Oil CompanyJan 1993 → Jun 2001
  2. 2Walsh & Watts, Inc.Jul 2001 → Nov 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
366117-99DrillFortson Oil CompanyNov 7, 1989Nov 10, 1989—7,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 10, 1990Yarbrough O-13-27620Dyemound S. (Bend Conglomerate)Walsh & Watts Inc.Plugged—

Formation tops

As filed on W-2/G-1. Subsea from 1,160 ft elevation.Download CSV →

FormationMD ftSubsea
Etter6,094-4,934
Caddo6,657-5,497
CaddoLOWER CADDO6,734-5,574

Perforations

Perforated and open-hole intervals.

FromToType
6,9587,016Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,07512.25485 S
5.57,2407.875400 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Feb 26, 1990Jan 19, 1990Yes
00Feb 9, 1990——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/33732816, documented in the API reference.