WELL · 42-221-31219 · DISTRICT 9

Randle #1H

Plugged

Hood County · Newark East (Barnett Shale) field  · Horizontal

Randle #1H (API 42-221-31219) is a plugged horizontal well in Hood County, plugged March 15, 2012, last operated by Premier Natural Resources II LLC.

The RRC has issued one drilling permit (amended once), issued October 18, 2006, permitted to 9,000 ft.

It was permitted by Burlington Resources O & G CO LP and has since transferred to Premier Natural Resources II LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Big Saline, Marble Falls, Barnett.

Operator of record

Premier Natural Resources II LLC

Permitted by Burlington Resources O & G Co LP; the EWA schedule now lists a different operator.

Based in
Tulsa, OK
P-5 status
Inactive (I)
P-5 last filed
Dec 22, 2014
Permits on file
9
Phone
(918) 392-3232

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePremier Natural Resources II LLC
Production reportsBurlington Resources O & G Co LPthrough Dec 2010
Latest permitBurlington Resources O & G Co LPOct 18, 2006

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

9,000
total depth, ft
2
permits on file
Oct 18, 2006
last permit issued
Feb 15, 2007
completed
0
cumulative oil, bbl
186K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2007 THROUGH Mar 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 15, 2007
Shut in
—
Plugged
Mar 15, 2012

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.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Randle G-13-232317Newark, East (Barnett Shale)Premier Natural Resources Ii,llc10186KFeb 2007 – Mar 2012

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Burlington Resources O & G Co LPMar 2007 → Dec 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
627643-98DrillBurlington Resources O & G Co LPOct 26, 2006Oct 18, 2006Oct 26, 20069,000
627643-99DrillBurlington Resources O & G Co LPOct 16, 2006Oct 18, 2006—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-232317————

Formation tops

As filed on W-2/G-1. Subsea from 950 ft elevation.Download CSV →

FormationMD ftSubsea
Big Saline4,435-3,485
Marble Falls4,631-3,681
Barnett5,098-4,148

Perforations

Perforated and open-hole intervals.

FromToType
6,6668,856Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62584612.25405 S
—5,880—290 S
—6,730—190 S
5.58,9877.875645 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 29, 2008May 3, 2007Yes
00Jan 17, 2008——

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