WELL · 42-429-34171 · DISTRICT 7

Dunigan #1

Y

Stephens County · Stephens County Regular (Gas) field · Producing  · Vertical

Dunigan #1 (API 42-429-34171) is a well in Stephens County operated by Petex, completed August 17, 1984 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 1, 1984, permitted to 4,500 ft.

It was permitted by Mcclymond Brothers, Inc. and has since transferred to Petex on the wellbore schedule.

Completion filings report 5 formation tops, including Strawns, Caddo, Conglomerate, Duffer.

No lease production has been reported under this well’s leases.

Operator of record

Petex

Permitted by McClymond Brothers, Inc.; the EWA schedule now lists a different operator.

Breckenridge, TX · P-5 Y, filed May 4, 2026 · 124 permits on file · (254) 559-5453

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetex
Production reportsPetexthrough Apr 2026
Latest permitMcClymond Brothers, Inc.Aug 1, 1984

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

4,500
total depth, ft
1
permits on file
Aug 1, 1984
last permit issued
Aug 17, 1984
completed
0
cumulative oil, bbl
413K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 17, 1984
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Dunigan G-8-113367Stephens County Regular (Gas)Petex10413KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 6,235 · prior 12 6,716(-7%)

05001K202420252026

Chain of custody

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

  1. 1McClymond, Inc.Jan 1993 → Jul 2001
  2. 2McClymond, Ltd.Aug 2001 → Dec 2003
  3. 3Breck Operating Corp.Jan 2004 → Jul 2019
  4. 4PetexAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
246957-99DrillMcClymond Brothers, Inc.Jul 30, 1984Aug 1, 1984—4,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-113367————

Formation tops

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

FormationMD ftSubsea
Strawns1,600-94
Caddo3,350-1,844
Conglomerate3,870-2,364
Duffer4,085-2,579
Ellenburger4,340-2,834

Perforations

Perforated and open-hole intervals.

FromToType
3,8703,877Perforated
4,0454,052Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62524212.25175 S
4.54,2557.875390 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
00Jan 24, 1986Jul 25, 1985—
00Nov 27, 1984Sep 21, 1984—
00Nov 14, 1984Sep 5, 1984—

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