WELL · 42-127-33398 · DISTRICT 1
Briscoe Catarina Ranch #1H
Dimmit County · Briscoe Ranch (Eagleford) field · Horizontal
Briscoe Catarina Ranch #1H (API 42-127-33398) is a horizontal well in Dimmit County operated by Anadarko E&P Company LP, completed August 29, 2008.
The RRC has issued 3 drilling permits between 2006 and 2008, permitted to 13,500 ft.
It was permitted by Txco Resources Inc. and has since transferred to Anadarko E&P Company LP on the wellbore schedule.
Completion filings report 6 formation tops, including Austin Chalk, Eagle Ford, Edwards, Glen Rose.
Its 4 leases have reported 17.4K barrels of oil and 539K mcf of gas since January 2007, last reporting in July 2026. The leases carry 4 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Txco Resources Inc.; the EWA schedule now lists a different operator.
Houston, TX · P-5 Y, filed Jul 4, 2025 · 2,635 permits on file · (832) 636-1111
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anadarko E&P Company LP |
| Production reports | Javelin Energy Partners Mgmt LLCthrough Apr 2026 |
| Latest permit | Txco Resources Inc.Jul 1, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 13,500
- total depth, ft
- 3
- permits on file
- Jul 1, 2008
- last permit issued
- Aug 29, 2008
- completed
- 17.4K
- cumulative oil, bbl
- 539K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2007 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 29, 2008
- Shut in
- —
- Plugged
- —
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 4 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Briscoe Catarina Ranch G-1-253227 | Briscoe Ranch (Eagleford) | Javelin Energy Partners Mgmt LLC | 1 | 0 | 422K | Sep 2009 – Jul 2026 |
| Briscoe Catarina Ranch O-1-15022 | Briscoe Ranch (Eagleford) | Anadarko E&P Company LP | 1 | 17.4K | 111K | Aug 2008 – Jan 2010 |
| Briscoe Catarina Ranch G-1-236237 | Briscoe Ranch (Eagleford) | Anadarko E&P Company LP | 1 | 0 | 5.12K | Nov 2007 – Aug 2009 |
| Briscoe Catarina Ranch G-1-231907 | Wildcat | Anadarko E&P Company LP | 1 | 0 | 0 | Jan 2007 – Nov 2007 |
Gas, mcf lease total
Last 12 months 6,920 · prior 12 6,408(+8%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Anadarko E&P Company LPNov 2007 → Dec 2012
- 2Txco Resources Inc.May 2008 → Sep 2008
- 3Anadarko E&P Onshore LLCJan 2013 → Feb 2017
- 4SN EF Maverick, LLCMar 2017 → Aug 2023
- 5Javelin Energy Partners Mgmt LLCSep 2023 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 664483-99 | Recompletion | Txco Resources Inc. | Jun 13, 2008 | Jul 1, 2008 | Jun 16, 2008 | 8,250 |
| 643872-99 | Recompletion | Anadarko E&P Company LP | Aug 6, 2007 | Aug 10, 2007 | Sep 1, 2007 | 11,840 |
| 626876-99 | Drill | Anadarko E&P Company LP | Oct 2, 2006 | Oct 3, 2006 | Nov 3, 2006 | 13,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-1-231907 | — | — | — | — |
| — | — G-1-236237 | — | — | — | — |
| — | — G-1-253227 | — | — | — | — |
| — | — O-1-15022 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 623 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin Chalk | 7,116 | -6,493 |
| Eagle FordEAGLEFORD | 7,443 | -6,820 |
| Eagle FordEAGLEFORD | 7,664 | -7,041 |
| Edwards | 8,528 | -7,905 |
| Glen Rose | 9,503 | -8,880 |
| Pearsall | 11,651 | -11,028 |
| Sligo | 12,300 | -11,677 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,443 | 11,094 | Perforated |
| 7,700 | 7,702 | Perforated |
| 7,910 | 7,960 | Perforated |
| 7,934 | 7,995 | Perforated |
| 8,206 | 11,094 | Perforated |
| 11,920 | 11,980 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 2,902 | 17.5 | 2,136 S |
| 5.5 | 8,550 | — | — |
| 9.625 | 11,530 | 12.25 | 1,460 S |
| 5.5 | 13,130 | 8.5 | 460 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 | Feb 3, 2010 | Oct 2, 2009 | — |
| 00 | Dec 8, 2009 | — | — |
| 00 | May 6, 2009 | Mar 23, 2009 | — |
| 00 | Mar 27, 2009 | — | — |
| 00 | Jul 9, 2008 | Nov 26, 2007 | Yes |
| 00 | Jun 27, 2008 | — | — |
| 00 | Jan 10, 2008 | Jul 30, 2007 | — |
| 00 | Jan 9, 2008 | Jun 5, 2007 | Yes |
| 00 | Dec 31, 2007 | — | — |
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-127-33398 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-127-33398 → 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/12733398, documented in the API reference.