TEXAS · WELLS · DENTON COUNTY · HIGGS UNIT LEASE · API 42-121-34174 · DISTRICT 7C
Higgs Unit #2H
Denton County · Newark East (Barnett Shale) field · Temp Abandoned · Horizontal
Higgs Unit #2H (API 42-121-34174) is a horizontal well in Denton County operated by Lime Rock Resources IV-A L.P., completed May 25, 2012 and listed as temp abandoned on the RRC schedule, shut in April 1, 2024.
The RRC has issued one drilling permit (amended once), issued May 27, 2011, permitted to 8,678 ft.
It was permitted by Burlington Resources O & G CO LP and has since transferred to Lime Rock Resources IV-A L.P. on the wellbore schedule.
Completion filings report 2 formation tops, including Barnett, Forestburg.
Its lease has reported 12.3K barrels of oil and 607K mcf of gas since May 2012, last reporting volume in March 2024.
Operator of record
Permitted by Burlington Resources O & G Co LP; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 18, 2025
- Permits on file
- 117
- Phone
- (713) 292-9510
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Lime Rock Resources IV-a L.P. |
| Production reports | Lime Rock Resources IV-a, L.P.through Jun 2024 |
| Latest permit | Burlington Resources O & G Co LPMay 27, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,678
- total depth, ft
- 2
- permits on file
- May 27, 2011
- last permit issued
- May 25, 2012
- completed
- 12.3K
- cumulative oil, bbl
- 607K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2012 THROUGH Jun 2024
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- May 25, 2012
- Shut in
- Apr 1, 2024
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Higgs Unit G-13-266212 | Newark, East (Barnett Shale) | Lime Rock Resources IV-a, L.P. | 1 | 12.3K | 607K | May 2012 – Jun 2024 |
Gas, mcf lease total
Last 12 months 0 · prior 12 0
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Burlington Resources O & G Co LPMay 2012 → Oct 2018
- 2Lime Rock Resources IV-a, L.P.Nov 2018 → Mar 2024
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 716851-98 | Drill | Burlington Resources O & G Co LP | Mar 21, 2012 | May 27, 2011 | Mar 24, 2012 | 9,000 |
| 716851-99 | Drill | Burlington Resources O & G Co LP | May 19, 2011 | May 27, 2011 | Mar 24, 2012 | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 25, 2012 | Higgs Unit G-13-266212 | Newark East (Barnett Shale) | Lime Rock Resources IV-a L.P. | Temp Abandoned · shut in Apr 1, 2024 | 8,678 |
Formation tops
As filed on W-2/G-1. Subsea from 915 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| BarnettUPPER BARNETT SHALE | 7,804 | -6,889 |
| Forestburg | 7,866 | -6,951 |
| BarnettLOWER BARNETT SHALE | 8,074 | -7,159 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,059 | 11,321 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,052 | 12.25 | 604 S |
| 5.5 | 11,395 | 8.75 | 1,336 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Mar 22, 2013 | Nov 14, 2012 | — |
| 00 | Feb 21, 2013 | Jun 22, 2012 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Jul 21, 2015. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Barnett, Forestburg | TIFF | 5,000 to 11,343 | Jul 21, 2015run Apr 3, 2012 | 0.48 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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.
- Wellbore filings for 42-121-34174 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-121-34174 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/12134174, documented in the API reference.