WELL · 42-025-32919 · DISTRICT 2
Barnhart #2
Bee County · Fred Long (Hockley 3850) field · Vertical
Barnhart #2 (API 42-025-32919) is a plugged well in Bee County, plugged December 28, 2018, last operated by Corenergy Operating Group LLC.
The RRC has issued one drilling permit (amended once), issued September 4, 1998, permitted to 4,800 ft.
Completion filings report one formation top, including Hockley.
Operator of record
Houston, TX · P-5 Y, filed Apr 4, 2026 · 58 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Corenergy Operating Group LLC |
| Production reports | Corenergy Operating Group, LLCthrough Mar 1999 |
| Latest permit | Corenergy Operating Group, LLCSep 4, 1998 |
- 4,800
- total depth, ft
- 2
- permits on file
- Sep 4, 1998
- last permit issued
- Oct 24, 1998
- completed
- 0
- cumulative oil, bbl
- 16.7K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 1998 THROUGH Dec 2018
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 24, 1998
- Shut in
- —
- Plugged
- Dec 28, 2018
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 |
|---|---|---|---|---|---|---|
| Barnhart G-2-172735 | Fred Long (Hockley 3850) | Corenergy Operating Group, LLC | 1 | 0 | 16.7K | Oct 1998 – Dec 2018 |
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.
- 1Corenergy Operating Group, LLCOct 1998 → Mar 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 479270-98 | Drill | Corenergy Operating Group, LLC | Feb 10, 1999 | Sep 4, 1998 | — | 4,800 |
| 479270-99 | Drill | Corenergy Operating Group, LLC | Sep 4, 1998 | Sep 4, 1998 | Sep 5, 1998 | 4,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-172735 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 268 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Hockley | 3,877 | -3,609 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,880 | 3,883 | Perforated |
| 3,885 | 3,888 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 643 | 12.25 | 265 S |
| 2.875 | 4,259 | 7.875 | 790 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 2, 1999 | Mar 2, 1999 | Yes |
| 00 | May 10, 1999 | — | — |
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-025-32919 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-32919 → scanned completion filings
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/02532919, documented in the API reference.