WELL · 42-479-38813 · DISTRICT 4
Briscoe N #1
Webb County · Vaquillas Ranch (Lobo Cons.) field · Vertical
Briscoe N #1 (API 42-479-38813) is a plugged well in Webb County, plugged March 10, 2015, last operated by Carrizo Oil & Gas Inc..
The RRC has issued one drilling permit, issued July 29, 2004, permitted to 9,500 ft.
Completion filings report 3 formation tops, including Lobo Unconformity, Lobo 3, Lobo 6.
Operator of record
Houston, TX · P-5 Inactive, filed Jan 7, 2021 · 1,194 permits on file · (713) 328-1000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Carrizo Oil & Gas Inc. |
| Production reports | Carrizo Oil & Gas, Inc.through Nov 2008 |
| Latest permit | Carrizo Oil & Gas, Inc.Jul 29, 2004 |
- 9,500
- total depth, ft
- 1
- permits on file
- Jul 29, 2004
- last permit issued
- Oct 4, 2004
- completed
- 0
- cumulative oil, bbl
- 91.8K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2004 THROUGH Mar 2015
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 4, 2004
- Shut in
- —
- Plugged
- Mar 10, 2015
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 |
|---|---|---|---|---|---|---|
| Briscoe N G-4-204720 | Vaquillas Ranch (Lobo Cons.) | Carrizo Oil & Gas, Inc. | 1 | 0 | 91.8K | Oct 2004 – Mar 2015 |
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.
- 1Carrizo Oil & Gas, Inc.Nov 2004 → Nov 2008
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 548877-99 | Drill | Carrizo Oil & Gas, Inc. | Jul 29, 2004 | Jul 29, 2004 | — | 9,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-204720 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 508 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Lobo Unconformity | 8,415 | -7,907 |
| Lobo 3 | 8,519 | -8,011 |
| Lobo 6 | 9,136 | -8,628 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,141 | 9,151 | Perforated |
| 9,266 | 9,276 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 750 | 12.25 | 325 S |
| 7 | 7,685 | 8.75 | 350 S |
| 2.875 | 9,500 | 6.125 | 335 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 24, 2005 | Nov 24, 2004 | Yes |
| 00 | Dec 21, 2004 | — | — |
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-479-38813 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-479-38813 → 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/47938813, documented in the API reference.