WELL · 42-143-31289 · DISTRICT 9

Rough Creek Unit #A 1H

Y

Erath County · Newark East (Barnett Shale) field · Temp Abandoned  · Horizontal

Rough Creek Unit #A 1H (API 42-143-31289) is a horizontal well in Erath County operated by TX H&H Oil CO. #1 LLC, completed January 23, 2009 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 5, 2008, permitted to 4,900 ft.

It was permitted by Rimrock Energy, LLC and has since transferred to TX H&H Oil CO. #1 LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Marble Falls, Barnett.

No lease production has been reported under this well’s leases.

Operator of record

TX H&H Oil Co. #1 LLC

Permitted by Rimrock Energy, LLC; the EWA schedule now lists a different operator.

Kilgore, TX · P-5 Y, filed Jan 5, 2026 · (254) 977-3826

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTX H&H Oil Co. #1 LLC
Production reportsRimrock Energy, LLCthrough Apr 2009
Latest permitRimrock Energy, LLCMar 5, 2008

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

4,900
total depth, ft
1
permits on file
Mar 5, 2008
last permit issued
Jan 23, 2009
completed
0
cumulative oil, bbl
5.79K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 23, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Rough Creek Unit G-13-249863Newark, East (Barnett Shale)TX H&H Oil Co. #1, LLC105.79KJan 2009 – Jul 2026

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. 1Rimrock Energy, LLCJan 2009 → Apr 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
655695-99DrillRimrock Energy, LLCFeb 20, 2008Mar 5, 2008Apr 16, 20084,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-249863————

Formation tops

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

FormationMD ftSubsea
Marble Falls4,241-3,096
Barnett4,687-3,542

Perforations

Perforated and open-hole intervals.

FromToType
5,3355,159Perforated
5,6555,479Perforated
5,9755,799Perforated
6,2956,119Perforated
6,4396,615Perforated
6,7596,935Perforated
7,0797,255Perforated
7,3997,575Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62582512.25285 S
5.57,6307.875740 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
00Sep 4, 2009Mar 23, 2009Yes
00Aug 4, 2009——

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