WELL · 42-231-30263 · DISTRICT 5

MP 307.1 CP Unit #1CP #1

N

Hunt County  · Vertical

MP 307.1 CP Unit #1cp #1 (API 42-231-30263) is a permitted well in Hunt County filed by Explorer Pipeline Company; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 2, 2014, permitted to 375 ft.

Operator of record

Explorer Pipeline Company

Tulsa, OK · P-5 Y, filed Jan 4, 2026 · 23 permits on file · (918) 493-5126

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitExplorer Pipeline CompanyJul 2, 2014
375
total depth, ft
1
permits on file
Jul 2, 2014
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

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
788514-99DrillExplorer Pipeline CompanyJun 3, 2014Jul 2, 2014—375

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