WELL · 42-479-39592 · DISTRICT 4

Briscoe E #304

Plugged

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

Briscoe E #304 (API 42-479-39592) is a plugged well in Webb County, plugged October 3, 2013, last operated by SM Energy Company.

The RRC has issued one drilling permit, issued July 26, 2006, permitted to 4,600 ft.

It was permitted by Huber Energy L.P. and has since transferred to SM Energy Company on the wellbore schedule.

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

Its lease has reported 20.5K barrels of oil and 227K mcf of gas since March 2005, last reporting in September 2014. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

SM Energy Company

Permitted by Huber Energy L.P.; 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 Apr 2014
Latest permitHuber Energy L.P.Jul 26, 2006

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

4,600
total depth, ft
1
permits on file
Jul 26, 2006
last permit issued
Jan 11, 2007
completed
20.5K
cumulative oil, bbl
227K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2005 THROUGH Sep 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 11, 2007
Shut in
—
Plugged
Oct 3, 2013

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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Briscoe "E" O-4-13329Gold River, North (Olmos)SM Energy Company320.5K227KMar 2005 – Sep 2014

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 L.P.Mar 2005 → Sep 2006
  2. 2Rockford Energy Partners II, LLCOct 2006 → Sep 2007
  3. 3St. Mary Land & Exploration Co.Oct 2007 → Jun 2010
  4. 4SM Energy CompanyJul 2010 → Nov 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
622811-99DrillHuber Energy L.P.Jul 18, 2006Jul 26, 2006Nov 22, 20064,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-13329————

Formation tops

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

FormationMD ftSubsea
Escondido2,158-1,629
Olmos3,774-3,245

Perforations

Perforated and open-hole intervals.

FromToType
4,1404,152Perforated
4,2264,248Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62576712.25315 S
4.54,5087.875740 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
00May 25, 2007May 4, 2007Yes
00May 24, 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.

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