WELL · 42-009-43424 · DISTRICT 13

Turbeville B #3

N

Archer County  · Vertical

Turbeville B #3 (API 42-009-43424) is a permitted well in Archer County filed by Eagle Oil & Gas CO.; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 12, 2026, permitted to 5,500 ft.

Operator of record

Eagle Oil & Gas Co.

Dallas, TX · P-5 Y, filed Jan 4, 2026 · 347 permits on file · (940) 781-0704

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitEagle Oil & Gas Co.May 12, 2026
5,500
total depth, ft
1
permits on file
May 12, 2026
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.442556, -98.620086

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
915456-99DrillEagle Oil & Gas Co.May 7, 2026May 12, 2026—5,500

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 →

Turbeville B42-009-43411

0.4 KM · Eagle Oil & Gas Co. · Section with this well →

Gunsight892193
Strawn2,743-1,658
Ward Sand—
Bryson—
Thomas Sand—
Megargel—
Delmar—
Davidson—

10 TOPS · FIRST 8

Turbeville B42-009-43391

0.4 KM · Eagle Oil & Gas Co. · Section with this well →

Gunsight880
Strawn2,738
Canyon—
Ward Sand—
Thomas Sand—
Megargel—
Delmar—
Davidson—

10 TOPS · FIRST 8

Andrews 'A'42-009-43386

1.0 KM · Borderline Operating Corp. · Section with this well →

Bryson4,338-3,233
Canyon—
Ward Sand—
Thomas Sand—
Strawn—
Megargel—
Gunsight—
Delmar—

10 TOPS · FIRST 8

Andrews 'B'42-009-43383

1.0 KM · B.O.L.D. Oil and Gas, LLC · Section with this well →

Bryson4,236-3,145
Canyon—
Cisco—
Davidson—
Delmar—
Gunsight—
Megargel—
Strawn—

10 TOPS · FIRST 8

Mustangs42-009-43412

1.0 KM · Eagle Oil & Gas Co. · Section with this well →

Strawn2,748-1,621
Cadoo4,564-3,437
Bryson—
Canyon—
Cisco—
Conglomerate—
Davidson—
Megargel—

10 TOPS · FIRST 8

Andrews Longley42-009-43378

1.3 KM · JMH Production, LLC · Section with this well →

Strawn4,304-3,209
Bryson—
Cisco—
Davidson—
Delmar—
Gunsight—
Megargel—
Thomas Sand—

10 TOPS · FIRST 8

Andrews 'A'42-009-43372

1.4 KM · Borderline Operating Corp. · Section with this well →

Canyon4,275-3,172
Bryson—
Cisco—
Davidson—
Delmar—
Gunsight—
Megargel—
Strawn—

10 TOPS · FIRST 8

Andrews 'A'42-009-43362

1.4 KM · Borderline Operating Corp. · Section with this well →

Gunsight886220
Bryson4,314-3,208
Strawn—
Megargel—
Delmar—
Davidson—
Cisco—
Ward Sand—

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