WELL · 42-503-39356 · DISTRICT 9

Walsh #1WD

Plugged

Young County · Young County Regular field  · Vertical

Walsh #1WD (API 42-503-39356) is a plugged well in Young County, plugged March 26, 2015, last operated by Antle Operating Inc..

The RRC has issued one drilling permit, issued October 14, 1986, permitted to 2,700 ft.

It was permitted by Antle, E. and has since transferred to Antle Operating Inc. on the wellbore schedule.

Its lease has reported 8.56K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Antle Operating Inc.

Permitted by Antle, E.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Oct 4, 2025 · 94 permits on file · (940) 329-1432

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAntle Operating Inc.
Production reportsAntle Operating, Inc.through Dec 2013
Latest permitAntle, E.Oct 14, 1986

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

2,700
total depth, ft
1
permits on file
Oct 14, 1986
last permit issued
Jan 28, 1987
completed
8.56K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 28, 1987
Shut in
—
Plugged
Mar 26, 2015

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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Walsh O-13-26304Young County RegularAntle Operating, Inc.38.56K21Jan 1993 – Jul 2026

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. 1Antle, E.Jan 1993 → Jun 1994
  2. 2Antle Operating, Inc.Jul 1994 → Dec 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
321700-99DrillAntle, E.Oct 10, 1986Oct 14, 1986—2,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-26304————

Perforations

Perforated and open-hole intervals.

FromToType
1,1491,169Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511412.2585 S
4.51,2657.875125 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 27, 1987Feb 4, 1987—
00Feb 11, 1987——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
103K
bbl, all reported
Nov 2014
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000062515W-14 DisposalPlugged Apr 9, 2015404501,149–1,169

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 60(-100%)

010203020132014

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/50339356, documented in the API reference.