WELL · 42-479-43920 · DISTRICT 1

Briscoe R #373H

Y

Webb County · Briscoe Ranch (Eagleford) field · Producing  · Horizontal

Briscoe R #373H (API 42-479-43920) is a horizontal well in Webb County operated by SM Energy Company, completed October 30, 2020 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 15, 2018, permitted to 10,000 ft.

Completion filings report 11 formation tops, including Wilcox, Escondido, Olmos, Eagle Ford.

No lease production has been reported under this well’s leases.

Operator of record

SM Energy Company

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 2026
Latest permitSM Energy CompanyFeb 15, 2018
10,000
total depth, ft
1
permits on file
Feb 15, 2018
last permit issued
Oct 30, 2020
completed
0
cumulative oil, bbl
2.29M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2018 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 30, 2020
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

28.046087, -99.926384

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Webb County.

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 R G-1-285803Briscoe Ranch (Eagleford)SM Energy Company102.29MOct 2018 – Jul 2026

Gas, mcf lease total

Last 12 months 152,036 · prior 12 156,140(-3%)

010K20K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1SM Energy CompanyOct 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
836238-99DrillSM Energy CompanyFeb 12, 2018Feb 15, 2018Jul 11, 201810,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-285803————

Formation tops

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

FormationMD ftSubsea
WilcoxWILCOX - INJECTION/DISPOSAL1,407-689
EscondidoESCONDITO - INJECTION/DISPOSAL;2,763-2,045
OlmosOLMOS - INJECTION/DISPOSAL4,107-3,389
Eagle FordEAGLE FORD SHALE7,460-6,742
CatahoulaCATAHOULA-FRIO - INJECTION/DISPO——
Cook Mountain——
EdwardsEDWARDS LIMESTONE - H2S——
JacksonJACKSON - INJECTION/DISPOSAL——
Queen CityQUEEN CITY - INJECTION/DISPOSAL;——
SligoSLIGO - H2S——
YeguaYEGUA - INJECTION/DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
8,12417,030Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,54812.25650 S
5.517,0758.52,925 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
00Sep 10, 2021Aug 12, 2021Yes
00Nov 20, 2020Nov 20, 2020—
00Sep 11, 2019Jun 7, 2019—
00Feb 20, 2019Jan 16, 2019Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Briscoe R (SA6)42-479-43911

0.0 KM · SM Energy Company · Section with this well →

Wilcox1,407-688
Escondido2,766-2,047
Olmos4,107-3,388
Eagle Ford7,461-6,742
Yegua—
Catahoula—
Cook Mountain—
Queen City—

10 TOPS · FIRST 8

Briscoe R (SA7)42-479-43916

0.0 KM · SM Energy Company · Section with this well →

Wilcox1,407-688
Escondido2,769-2,050
Olmos4,104-3,385
Eagle Ford7,466-6,747
Cook Mountain—
Catahoula—
Edwards—
Jackson—

10 TOPS · FIRST 8

Briscoe R42-479-41366

0.6 KM · SM Energy Company · Section with this well →

Anacacho6,774-6,064
Eagle Ford7,116-6,406
Austin Chalk7,151-6,441
Eagle Ford7,514-6,804
Eagle Ford7,678-6,968

Briscoe R (SA26) State42-479-44746

1.2 KM · SM Energy Company · Section with this well →

Wilcox1,374-650
Midway2,417-1,693
Escondido2,761-2,037
Olmos3,997-3,273
San Miguel5,849-5,125
Yegua—
Eagle Ford—
Cook Mountain—

12 TOPS · FIRST 8

Briscoe R (SA27) State42-479-44747

1.3 KM · SM Energy Company · Section with this well →

Wilcox1,374-651
Midway2,417-1,694
Escondido2,761-2,038
Olmos3,997-3,274
San Miguel5,849-5,126
Yegua—
Catahoula—
Cook Mountain—

12 TOPS · FIRST 8

Pge Dos42-479-44587

1.4 KM · Chesapeake Operating, L.L.C. · Section with this well →

Jackson69046
Queen City900-164
Yegua1,100-364
Catahoula1,500-764
Wilcox1,800-1,064
Escondido3,007-2,271
Cook Mountain3,970-3,234
Olmos4,208-3,472

10 TOPS · FIRST 8

Pge Dos42-479-44593

1.4 KM · Chesapeake Operating, L.L.C. · Section with this well →

Jackson69046
Queen City900-164
Yegua1,100-364
Catahoula1,500-764
Wilcox1,800-1,064
Escondido3,006-2,270
Cook Mountain3,970-3,234
Olmos4,226-3,490

10 TOPS · FIRST 8

Pge Dos42-479-44588

1.4 KM · Chesapeake Operating, L.L.C. · Section with this well →

Jackson69047
Queen City900-163
Yegua1,100-363
Catahoula1,500-763
Wilcox1,800-1,063
Escondido3,018-2,281
Cook Mountain3,970-3,233
Olmos4,229-3,492

12 TOPS · FIRST 8

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