WELL · 42-207-32779 · DISTRICT 8

Coody #O 1

Plugged

Haskell County · Haskell County Regular field  · Vertical

Coody #O 1 (API 42-207-32779) is a plugged well in Haskell County, plugged May 23, 2016, last operated by Oakridge Oil And Gas LP.

The RRC has issued one drilling permit, issued July 26, 2013, permitted to 6,000 ft.

It was permitted by Oakridge Oil And Gas, LP and has since transferred to Oakridge Oil And Gas LP on the wellbore schedule.

Operator of record

Oakridge Oil and Gas LP

Permitted by Oakridge Oil and Gas, LP; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitOakridge Oil and Gas, LPJul 26, 2013

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

6,000
total depth, ft
1
permits on file
Jul 26, 2013
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
May 23, 2016

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.

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
766777-99DrillOakridge Oil and Gas, LPJul 19, 2013Jul 26, 2013—6,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.

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