WELL · 42-321-32019 · DISTRICT 3
Doss William #1
Matagorda County · Lake Austin State (Mio. 15 SD) field · Vertical
Doss William #1 (API 42-321-32019) is a plugged well in Matagorda County, plugged June 29, 2011, last operated by Bexco Operating Inc..
The RRC has issued one drilling permit, issued August 9, 2004, permitted to 9,000 ft.
Completion filings report 3 formation tops, including M-13 Sd, M-14.5 Sd, M-15 Sd.
Operator of record
College Sta, TX · P-5 Y, filed Jun 5, 2020 · 156 permits on file · (979) 224-1189
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Bexco Operating Inc. |
| Production reports | Bexco Operating, Inc.through Jun 2011 |
| Latest permit | Bexco Operating, Inc.Aug 9, 2004 |
- 9,000
- total depth, ft
- 1
- permits on file
- Aug 9, 2004
- last permit issued
- Sep 27, 2004
- completed
- 0
- cumulative oil, bbl
- 1.88M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2004 THROUGH Jun 2011
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 27, 2004
- Shut in
- —
- Plugged
- Jun 29, 2011
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 |
|---|---|---|---|---|---|---|
| Doss, William G-3-204433 | Lake Austin State (Mio. 15 SD) | Bexco Operating, Inc. | 1 | 0 | 1.88M | Sep 2004 – Jun 2011 |
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.
- 1Bexco Operating, Inc.Oct 2004 → Jun 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 549349-99 | Drill | Bexco Operating, Inc. | Aug 9, 2004 | Aug 9, 2004 | Sep 6, 2004 | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-3-204433 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 5 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| M-13 SD | 5,650 | -5,645 |
| M-14.5 SD | 5,920 | -5,915 |
| M-15 SD | 6,737 | -6,732 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,359 | 6,361 | Perforated |
| 6,376 | 6,378 | Perforated |
| 6,389 | 6,392 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,614 | 12.25 | 564 S |
| 4.5 | 6,737 | 8.75 | 815 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 | Feb 24, 2005 | Nov 1, 2004 | Yes |
| 00 | Dec 6, 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.
- Wellbore filings for 42-321-32019 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-321-32019 → 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/32132019, documented in the API reference.