WELL · 42-357-33089 · DISTRICT 14

Duke WB #1

Plugged

Ochiltree County  · Vertical

Duke WB #1 (API 42-357-33089) is a plugged well in Ochiltree County, plugged April 13, 2013, last operated by Mfp Petroleum Ltd. Partnership.

The RRC has issued 2 drilling permits between 2012 and 2013, permitted to 9,000 ft.

Operator of record

MFP Petroleum Ltd. Partnership

Oklahoma City, OK · P-5 Y, filed Nov 3, 2017 · 3 permits on file · (405) 728-5588

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMFP Petroleum Ltd. PartnershipMar 19, 2013
9,000
total depth, ft
2
permits on file
Mar 19, 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
Apr 13, 2013

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
757740-99ReenterMFP Petroleum Ltd. PartnershipMar 1, 2013Mar 19, 2013Feb 25, 20139,000
733669-99DrillGunn Oil CompanyFeb 10, 2012Feb 23, 2012Feb 29, 20129,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/35733089, documented in the API reference.