WELL · 42-175-34054 · DISTRICT 2
Pettus T. W. #1
Goliad County · Berclair (2800) field · Vertical
Pettus T. W. #1 (API 42-175-34054) is a plugged well in Goliad County, plugged February 7, 2012, last operated by Welder Exploration & Prod. Inc..
The RRC has issued one drilling permit (amended once), issued January 3, 2008, permitted to 4,000 ft.
Operator of record
Welder Exploration & Prod. Inc.
- Based in
- San Antonio, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Mar 9, 2023
- Permits on file
- 346
- Phone
- (210) 354-1515
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Welder Exploration & Prod. Inc. |
| Production reports | Welder Exploration & Prod., Inc.through Jun 2011 |
| Latest permit | Welder Exploration & Prod., Inc.Jan 3, 2008 |
- 4,000
- total depth, ft
- 2
- permits on file
- Jan 3, 2008
- last permit issued
- Sep 21, 2009
- completed
- 0
- cumulative oil, bbl
- 78.9K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2008 THROUGH Feb 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 21, 2009
- Shut in
- —
- Plugged
- Feb 7, 2012
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 |
|---|---|---|---|---|---|---|
| Pettus, T. W. G-2-241920 | Berclair (2800) | Welder Exploration & Prod., Inc. | 1 | 0 | 78.9K | Sep 2008 – Feb 2012 |
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.
- 1Welder Exploration & Prod., Inc.Oct 2008 → Jun 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 652012-98 | Drill | Welder Exploration & Prod., Inc. | Sep 11, 2008 | Jan 3, 2008 | Sep 2, 2008 | 4,000 |
| 652012-99 | Drill | Welder Exploration & Prod., Inc. | Dec 21, 2007 | Jan 3, 2008 | Sep 2, 2008 | 4,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-241920 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,748 | 2,750 | Perforated |
| 2,962 | 2,968 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 729 | 12.25 | 320 S |
| 2.875 | 3,571 | — | 730 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 | Mar 7, 2009 | Jan 30, 2009 | — |
| 00 | Jan 15, 2009 | Nov 14, 2008 | — |
| 00 | Nov 20, 2008 | Oct 22, 2008 | Yes |
| 00 | Nov 10, 2008 | — | — |
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-175-34054 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-175-34054 → 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/17534054, documented in the API reference.