WELL · 42-419-30479 · DISTRICT 6
Smith Gas Unit #1
Shelby County · Vertical
Smith Gas Unit #1 (API 42-419-30479) is a plugged well in Shelby County, plugged March 19, 1984, last operated by Mustang Drilling, Ltd..
The RRC has issued 2 drilling permits between 1984 and 2005, permitted to 9,200 ft.
Completion filings report 4 formation tops, including BMA, Pettit, Travis Peak, "B" Lime.
Operator of record
Henderson, TX · P-5 Y, filed Feb 6, 2009 · 32 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Mustang Drilling, Inc.through Mar 2013 |
| Latest permit | Mustang Drilling, Ltd.May 13, 2005 |
- 9,200
- total depth, ft
- 2
- permits on file
- May 13, 2005
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 33.8K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2005 THROUGH Jul 2014
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Mar 19, 1984
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 |
|---|---|---|---|---|---|---|
| Smith Gas Unit G-6-213955 | CCB (Travis Peak) | Mustang Drilling, Inc. | 1 | 0 | 33.8K | Aug 2005 – Jul 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.
- 1Mustang Drilling, Ltd.Nov 2005 → May 2008
- 2Mustang Drilling, Inc.Jun 2008 → Mar 2013
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 600619-99 | Reenter | Mustang Drilling, Ltd. | May 13, 2005 | May 13, 2005 | — | 9,200 |
| 228737-99 | Drill | Gatoil (U.S.A.), Inc. | Feb 6, 1984 | Feb 7, 1984 | Feb 23, 1984 | 7,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-213955 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 294 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| BMA | 5,586 | -5,292 |
| Pettit | 6,334 | -6,040 |
| Travis Peak | 6,914 | -6,620 |
| "B" Lime | 9,043 | -8,749 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,891 | 9,010 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,521 | 11 | 725 S |
| 4.5 | 9,200 | 7.875 | 1,350 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 | May 26, 2006 | Aug 30, 2005 | Yes |
| 00 | Feb 15, 2006 | — | — |
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-419-30479 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-419-30479 → 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/41930479, documented in the API reference.