TEXAS · WELLS · REFUGIO COUNTY · API 42-391-33187 · DISTRICT 02

Heard J.P. #1

Plugged

Refugio County · Refugio-Fox (5900) field  · Vertical

Heard J.P. #1 (API 42-391-33187) is a plugged well in Refugio County, plugged November 13, 2018, last operated by Millennium Exploration CO. LLC.

The RRC has issued one drilling permit, issued January 29, 2018, permitted to 6,300 ft.

It was permitted by Millennium Exploration CO. LLC and has since transferred to Millennium Exploration CO. LLC on the wellbore schedule.

Operator of record

Millennium Exploration Co. LLC

Permitted by Millennium Exploration Co. LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMillennium Exploration Co. LLCJan 29, 2018

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

6,300
total depth, ft
1
permits on file
Jan 29, 2018
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
Nov 13, 2018

Surface location

28.328728, -97.344788

Google Maps ↗

Permit surface location from the RRC GIS record, in Refugio 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
835416-99DrillMillennium Exploration Co. LLCJan 19, 2018Jan 29, 2018Mar 30, 20186,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 neighbors can.

Section of the neighbors →

Rooke, P. H.42-391-03059

2.7 KM · Kamlok Oil & Gas, Inc. · Section with this well →

Frio—
Jackson—
Catahoula—

Rook, P.H.42-391-33275

2.8 KM · San Isidro Development Co, L. C. · Section with this well →

Catahoula3,660-3,599
Frio3,970-3,909
Jackson—

Rooke42-391-33253

3.1 KM · Acock/Anaqua Operating Co., LP · Section with this well →

Catahoula3,595-3,548
Frio3,900-3,853
Frio6,150-6,103
Jackson—

Rooke, P.H.42-391-33220

3.2 KM · Acock/Anaqua Operating Co., LP · Section with this well →

Catahoula3,540-3,514
Frio3,880-3,854
Jackson—

Rooke42-391-33173

3.3 KM · Acock/Anaqua Operating Co., LP · Section with this well →

Catahoula3,540-3,501
Frio3,858-3,819
Jackson—

Rooke42-391-33237

3.4 KM · San Isidro Development Co, L. C. · Section with this well →

Catahoula3,590-3,543
Frio4,410-4,363
Jackson—

Rooke42-391-33208

3.5 KM · Acock/Anaqua Operating Co., LP · Section with this well →

Catahoula1,600-1,567
Frio1,800-1,767
Jackson1,900-1,867

Miguelita Scanio42-391-33197

7.9 KM · Acock/Anaqua Operating Co., LP · Section with this well →

Catahoula1,600-1,565
Frio1,800-1,765
Jackson1,900-1,865

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