TEXAS · WELLS · HIDALGO COUNTY · BARRERA UNIT LEASE · API 42-215-33731 · DISTRICT 04
Barrera Unit #15
Hidalgo County · McMoran (8960) field · Producing · Directional
Barrera Unit #15 (API 42-215-33731) is a well in Hidalgo County operated by Hilcorp Energy Company, completed August 15, 2008 and listed as producing on the RRC schedule, shut in February 1, 2019.
The RRC has issued one drilling permit (amended once), issued November 21, 2007, permitted to 10,955 ft.
It was permitted by Chesapeake Operating, Inc. and has since transferred to Hilcorp Energy Company on the wellbore schedule.
Completion filings report 2 formation tops, including Frio, Vicksburg.
Its lease has reported 27.6K barrels of oil and 922K mcf of gas since August 2008, with no volume in the three years through April 2026.
Operator of record
Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 27, 2026
- Permits on file
- 3,458
- Phone
- (713) 209-2400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hilcorp Energy Company |
| Production reports | Hilcorp Energy Companythrough Jul 2024 |
| Latest permit | Chesapeake Operating, Inc.Apr 14, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,955
- total depth, ft
- 2
- permits on file
- Apr 14, 2008
- last permit issued
- Aug 15, 2008
- completed
- 27.6K
- cumulative oil, bbl
- 922K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2008 THROUGH Jul 2024
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 15, 2008
- Shut in
- Feb 1, 2019
- 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 |
|---|---|---|---|---|---|---|
| Barrera Unit G-4-242559 | McMoran (8960) | Hilcorp Energy Company | 1 | 27.6K | 922K | Aug 2008 – Jul 2024 |
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.
- 1Chesapeake Operating, Inc.Aug 2008 → Aug 2014
- 2Hilcorp Energy CompanySep 2014 → Mar 2022
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 648136-98 | Drill | Chesapeake Operating, Inc. | Mar 31, 2008 | Apr 14, 2008 | Apr 21, 2008 | 14,000 |
| 648136-99 | Drill | Chesapeake Operating, Inc. | Oct 19, 2007 | Nov 21, 2007 | — | 14,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 15, 2008 | Barrera Unit G-4-242559 | McMoran (8960) | Hilcorp Energy Company | Producing · shut in Feb 1, 2019 | 10,955 |
Formation tops
As filed on W-2/G-1. Subsea from 207 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,576 | 9,610 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 3,024 | 17.5 | 560 S |
| 9.625 | 8,210 | 12.25 | 480 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 | Dec 16, 2008 | Sep 15, 2008 | Yes |
| 00 | Dec 2, 2008 | — | — |
Well logs
3 logs loaded from the RRC's log index, the latest received Aug 29, 2011. Density, Neutron, 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 Vicksburg | TIFF | 9,870 to 11,194 | Aug 29, 2011run Jul 9, 2008 | 1.73 |
| COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Frio, Vicksburg | TIFF | 5,000 to 9,864 | Aug 29, 2011run Jun 29, 2008 | 5.45 |
| COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Frio, Vicksburg | TIFF | 3,011 to 7,892 | Aug 26, 2011run May 11, 2008 | 2.66 |
"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-215-33731 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-215-33731 → 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/21533731, documented in the API reference.