TEXAS · WELLS · MCMULLEN COUNTY · SBR LEASE · API 42-311-33273 · DISTRICT 01

SBR #100

Plugged

McMullen County · A.W.P. (Olmos) field  · Vertical

Sbr #100 (API 42-311-33273) is a plugged well in Mcmullen County, plugged July 21, 2015, last operated by Swift Energy Operating LLC.

The RRC has issued one drilling permit, issued October 10, 1996, permitted to 11,500 ft.

It was permitted by Swift Energy Company and has since transferred to Swift Energy Operating LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Sparta, Queen City, Carrizo, Wilcox.

Operator of record

Swift Energy Operating LLC

Permitted by Swift Energy Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
May 3, 2017
Permits on file
630
Phone
(281) 874-2700

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSwift Energy Operating LLC
Production reportsSwift Energy Companythrough Apr 1998
Latest permitSwift Energy CompanyOct 10, 1996

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

11,500
total depth, ft
1
permits on file
Oct 10, 1996
last permit issued
Dec 9, 1996
completed
0
cumulative oil, bbl
75.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1996 THROUGH Jul 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 9, 1996
Shut in
—
Plugged
Jul 21, 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
SBR G-1-161143A.W.P. (Olmos)Swift Energy Operating, LLC1075.6KDec 1996 – Jul 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. 1Swift Energy CompanyDec 1996 → Apr 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
453699-99DrillSwift Energy CompanyOct 10, 1996Oct 10, 1996Nov 20, 199611,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 9, 1996SBR G-1-161143A.W.P. (Olmos)Swift Energy Operating LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Sparta3,296-3,106
Queen City3,602-3,412
Carrizo5,229-5,039
Wilcox7,320-7,130
Lower Wade7,428-7,238
Navarro9,782-9,592
Olmos10,786-10,596

Perforations

Perforated and open-hole intervals.

FromToType
10,81010,830Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,5009.875312 S
7.6251,5009.875312 S
3.511,0186.51,180 S
8.625———

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 13, 1997Jul 3, 1997—
00Jan 30, 1997Jan 17, 1997Yes
00Jan 29, 1997——

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