WELL · 42-009-43392 · DISTRICT 9

JT Richardson Abc #37A

Plugged

Archer County · Archer County Regular field  · Vertical

JT Richardson Abc #37A (API 42-009-43392) is a plugged well in Archer County, plugged August 7, 2025, last operated by Guidance Oil Developers.

The RRC has issued one drilling permit, issued July 10, 2025, permitted to 1,300 ft.

It was permitted by Guidance Oil Developers and has since transferred to Guidance Oil Developers on the wellbore schedule.

Operator of record

Guidance Oil Developers

Permitted by Guidance Oil Developers; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitGuidance Oil DevelopersJul 10, 2025

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

1,300
total depth, ft
1
permits on file
Jul 10, 2025
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
Aug 7, 2025

Surface location

33.430078, -98.761852

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
909135-99DrillGuidance Oil DevelopersJul 9, 2025Jul 10, 2025Aug 7, 20251,300

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 →

Richardson Abc42-009-43235

0.2 KM · Guidance Oil Developers · Section with this well →

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

10 TOPS · FIRST 8

Richardson, J. T. 'Abc'42-009-43346

0.2 KM · Guidance Oil Developers · Section with this well →

Gunsight1,193
Thomas Sand—
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Richardson, J. T. 'Abc'42-009-43236

0.3 KM · Guidance Oil Developers · Section with this well →

Gunsight1,186
Bryson—
Thomas Sand—
Strawn—
Megargel—
Ward Sand—
Delmar—
Davidson—

10 TOPS · FIRST 8

Richardson, J. T. 'Abc'42-009-43249

0.3 KM · Guidance Oil Developers · Section with this well →

Gunsight1,195
Ward Sand—
Cadoo—
Cisco—
Conglomerate—
Davidson—
Delmar—
Marble Falls—

10 TOPS · FIRST 8

Richardson, J. T. Abc42-009-43241

0.3 KM · Guidance Oil Developers · Section with this well →

Gunsight1,182
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Thomas Sand—
Ward Sand—

10 TOPS · FIRST 8

Richardson, J. T. 'Abc'42-009-43242

0.3 KM · Guidance Oil Developers · Section with this well →

Gunsight1,187
Ward Sand—
Canyon—
Bryson—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Richardson, J. T. Abc42-009-43245

0.4 KM · Guidance Oil Developers · Section with this well →

Gunsight1,186
Strawn—
Megargel—
Bryson—
Ward Sand—
Thomas Sand—
Delmar—
Davidson—

10 TOPS · FIRST 8

Richardson, J. T. 'Abc'42-009-43399

0.5 KM · Guidance Oil Developers · Section with this well →

Gunsight1,280-10
Bryson—
Cisco—
Davidson—
Canyon—
Delmar—
Megargel—
Strawn—

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