WELL · 42-203-32809 · DISTRICT 6
Rudd W. L. A #6
Harrison County · Longwood (Goodland Lime) field · Temp Abandoned · Vertical
Rudd W. L. A #6 (API 42-203-32809) is a well in Harrison County operated by Wilcox Operating Corporation, completed September 30, 2003 and listed as temp abandoned on the RRC schedule.
The RRC has issued one drilling permit, issued May 29, 2003, permitted to 2,500 ft.
Completion filings report 3 formation tops, including Nacatoch, Blossom, Fredericksburg.
No lease production has been reported under this well’s leases.
Operator of record
Shreveport, LA · P-5 Y, filed Dec 4, 2025 · 31 permits on file · (318) 470-3655
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Wilcox Operating Corporation |
| Production reports | Wilcox Operating Corporationthrough Nov 2013 |
| Latest permit | Wilcox Operating CorporationMay 29, 2003 |
- 2,500
- total depth, ft
- 1
- permits on file
- May 29, 2003
- last permit issued
- Sep 30, 2003
- completed
- 0
- cumulative oil, bbl
- 88.7K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2003 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Sep 30, 2003
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Delinquent
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 |
|---|---|---|---|---|---|---|
| Rudd, W. L. "A" G-6-198174 | Longwood (Goodland Lime) | Wilcox Operating Corporation | 1 | 0 | 88.7K | Sep 2003 – Jul 2026 |
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.
- 1Wilcox Operating CorporationNov 2003 → Nov 2013
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 532324-99 | Drill | Wilcox Operating Corporation | May 23, 2003 | May 29, 2003 | Aug 8, 2003 | 2,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-198174 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 270 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,330 | 2,350 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 338 | 12.25 | 220 S |
| 4.5 | 2,400 | 7.875 | 650 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 | Jan 22, 2004 | Nov 6, 2003 | Yes |
| 00 | Dec 29, 2003 | — | — |
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-203-32809 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-203-32809 → 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/20332809, documented in the API reference.