WELL · 42-009-43103 · DISTRICT 13

Abby #30

N

Archer County  · Vertical

Abby #30 (API 42-009-43103) is a permitted well in Archer County filed by Ddc Production Company; no completion report is on file yet.

The RRC has issued one drilling permit, issued June 5, 2017, permitted to 2,000 ft.

Operator of record

DDC Production Company

Archer City, TX · P-5 Y, filed Aug 4, 2025 · 10 permits on file · (940) 733-5081

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitDDC Production CompanyJun 5, 2017
2,000
total depth, ft
1
permits on file
Jun 5, 2017
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

33.541656, -98.647585

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Archer County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
826453-99DrillDDC Production CompanyMay 9, 2017Jun 5, 2017—2,000

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Abby42-009-43104

0.2 KM · DDC Production Company · Section with this well →

Thomas Sand916
Gunsight1,159
Delmar—
Megargel—
Strawn—
Ward Sand—
Canyon—
Davidson—

10 TOPS · FIRST 8

Abby42-009-43102

0.3 KM · DDC Production Company · Section with this well →

Thomas Sand919
Gunsight1,161
Cisco—
Davidson—
Strawn—
Canyon—
Bryson—
Ward Sand—

10 TOPS · FIRST 8

Ikard42-009-43106

4.5 KM · HW Operating, LLC · Section with this well →

Thomas Sand910131
Gunsight1,01229
Strawn2,740-1,699
Caddo4,675-3,634
Megargel—
Canyon—
Cisco—
Davidson—

10 TOPS · FIRST 8

J. D. Hull42-009-43160

5.4 KM · Kelly Mahler Operating, LLC · Section with this well →

Thomas Sand600510
Gunsight1,120-10
Megargel—
Delmar—
Davidson—
Cisco—
Canyon—
Bryson—

10 TOPS · FIRST 8

Arnold, C S42-009-43112

5.6 KM · WMG Enterprises II, Inc. · Section with this well →

Gunsight1,110336
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—
Strawn—

10 TOPS · FIRST 8

Cowan & McKinney-50-42-009-43139

7.1 KM · Genepa Petroleum Company · Section with this well →

Thomas Sand900
Gunsight1,126
Ward Sand—
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—

10 TOPS · FIRST 8

Cowan & McKinney-50-42-009-43138

7.1 KM · Genepa Petroleum Company · Section with this well →

Thomas Sand900
Gunsight1,205
Bryson—
Ward Sand—
Strawn—
Megargel—
Delmar—
Davidson—

10 TOPS · FIRST 8

Cowan & McKinney-50-42-009-43140

7.3 KM · Genepa Petroleum Company · Section with this well →

Thomas Sand900
Gunsight1,122
Canyon—
Davidson—
Delmar—
Megargel—
Strawn—
Bryson—

10 TOPS · FIRST 8

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