WELL · 42-009-43325 · DISTRICT 13

Fish D. W. #36

Plugged

Archer County · Archer County Regular field  · Vertical

Fish D. W. #36 (API 42-009-43325) is a plugged well in Archer County, plugged August 11, 2023, last operated by Guidance Oil Developers.

The RRC has issued one drilling permit, issued March 15, 2023, permitted to 1,999 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 DevelopersMar 15, 2023

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

1,999
total depth, ft
1
permits on file
Mar 15, 2023
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 11, 2023

Surface location

33.565373, -98.728114

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
888970-99DrillGuidance Oil DevelopersMar 10, 2023Mar 15, 2023Mar 15, 20231,999

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 →

D.W. Fish42-009-43404

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

Gunsight1,404
Thomas Sand—
Strawn—
Ward Sand—
Bryson—
Canyon—
Cisco—
Davidson—

10 TOPS · FIRST 8

D. W. Fish42-009-43319

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

Thomas Sand1,180
Gunsight1,399
Davidson—
Ward Sand—
Strawn—
Megargel—
Delmar—
Cisco—

10 TOPS · FIRST 8

Luig42-009-43122

3.1 KM · Brower Oil & Gas Co., Inc. · Section with this well →

Thomas Sand1,185-156
Gunsight1,367-338
Bryson—
Ward Sand—
Cisco—
Canyon—
Davidson—
Delmar—

10 TOPS · FIRST 8

Luig42-009-43225

3.4 KM · Brower Oil & Gas Co., Inc. · Section with this well →

Strawn3,741-2,724
Delmar—
Cisco—
Canyon—
Davidson—
Ward Sand—
Bryson—
Megargel—

10 TOPS · FIRST 8

Luig42-009-43156

3.4 KM · Brower Oil & Gas Co., Inc. · Section with this well →

Thomas Sand1,140-114
Gunsight1,399-373
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Harvey42-009-43190

4.9 KM · Brower Oil & Gas Co., Inc. · Section with this well →

Bryson—
Ward Sand—
Thomas Sand—
Strawn—
Megargel—
Gunsight—
Delmar—
Davidson—

10 TOPS · FIRST 8

Harris Unit42-009-43174

5.2 KM · Eratz Investments Inc. · Section with this well →

Thomas Sand520602
Cisco940182
Gunsight1,010112
Ward Sand1,020102
Delmar1,03092
Megargel1,300-178
Strawn1,520-398
Davidson1,800-678

10 TOPS · FIRST 8

Harris Unit42-009-43261

5.5 KM · Ruthson Energy, Inc. · Section with this well →

Thomas Sand520580
Cisco940160
Gunsight1,01090
Ward Sand1,02080
Delmar1,03070
Megargel1,300-200
Strawn1,520-420
Davidson1,800-700

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