WELL · 42-479-38652 · DISTRICT 4

Briscoe J #34

Plugged

Webb County · Gold River North (Olmos) field  · Vertical

Briscoe J #34 (API 42-479-38652) is a plugged well in Webb County, plugged January 13, 2015, last operated by SM Energy Company.

The RRC has issued one drilling permit, issued March 4, 2004, permitted to 6,500 ft.

It was permitted by Crimson Energy Company, LC and has since transferred to SM Energy Company on the wellbore schedule.

Completion filings report 2 formation tops, including Escondido, Olmos.

Operator of record

SM Energy Company

Permitted by Crimson Energy Company, LC; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 2,485 permits on file · (432) 563-8316

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSM Energy Company
Production reportsSM Energy Companythrough Nov 2014
Latest permitCrimson Energy Company, LCMar 4, 2004

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

6,500
total depth, ft
1
permits on file
Mar 4, 2004
last permit issued
Apr 9, 2004
completed
0
cumulative oil, bbl
49.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2004 THROUGH Jan 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 9, 2004
Shut in
—
Plugged
Jan 13, 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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Briscoe "J" G-4-202186Gold River, North (Olmos)SM Energy Company1049.4KApr 2004 – Jan 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.

  1. 1Huber Energy Panhandle L.P.Apr 2004 → Sep 2004
  2. 2Huber Energy L.P.Oct 2004 → Sep 2006
  3. 3Rockford Energy Partners II, LLCOct 2006 → Sep 2007
  4. 4St. Mary Land & Exploration Co.Oct 2007 → Jun 2010
  5. 5SM Energy CompanyJul 2010 → Nov 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
542802-99DrillCrimson Energy Company, LCMar 4, 2004Mar 4, 2004Mar 20, 20046,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-202186————

Formation tops

As filed on W-2/G-1. Subsea from 550 ft elevation.Download CSV →

FormationMD ftSubsea
Escondido2,899-2,349
Olmos4,190-3,640

Perforations

Perforated and open-hole intervals.

FromToType
4,7064,721Perforated
4,7304,763Perforated
4,7694,778Perforated
4,7944,804Perforated
4,8264,844Perforated
4,9124,922Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,13212.25450 S
4.55,2287.8751,000 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Aug 20, 2004Jun 14, 2004Yes
00Jul 16, 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.

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/47938652, documented in the API reference.