WELL · 42-355-33462 · DISTRICT 4
Chapman Ranch #680
Nueces County · Chapman Ranch (Miocene Cons.) field · Vertical
Chapman Ranch #680 (API 42-355-33462) is a plugged well in Nueces County, plugged December 22, 2008, last operated by Decker Operating CO. L.L.C..
The RRC has issued one drilling permit, issued May 28, 2002, permitted to 3,000 ft.
Completion filings report one formation top, including Q-32.
Operator of record
Houston, TX · P-5 Y, filed Jan 4, 2026 · 137 permits on file · (361) 289-1641
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Decker Operating Co. L.L.C. |
| Production reports | Decker Operating Co., L.L.C.through May 2005 |
| Latest permit | Decker Operating Co., L.L.C.May 28, 2002 |
- 3,000
- total depth, ft
- 1
- permits on file
- May 28, 2002
- last permit issued
- Oct 27, 2004
- completed
- 0
- cumulative oil, bbl
- 301K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2002 THROUGH Dec 2008
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 27, 2004
- Shut in
- —
- Plugged
- Dec 22, 2008
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 |
|---|---|---|---|---|---|---|
| Chapman Ranch G-4-189542 | Chapman Ranch (Q-32) | Decker Operating Co., L.L.C. | 1 | 0 | 301K | Jun 2002 – Dec 2008 |
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.
- 1Decker Operating Co., L.L.C.Jun 2002 → May 2005
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 520405-99 | Drill | Decker Operating Co., L.L.C. | May 28, 2002 | May 28, 2002 | May 31, 2002 | 3,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-189542 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 37 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Q-32 | 2,601 | -2,564 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,529 | 2,532 | Perforated |
| 2,601 | 2,607 | Perforated |
| 2,618 | 2,622 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 550 | 12.25 | 270 S |
| 2.875 | 2,676 | 7.875 | 720 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, 2005 | Nov 24, 2004 | — |
| 00 | Aug 13, 2002 | Jul 19, 2002 | Yes |
| 00 | Jul 29, 2002 | — | — |
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-355-33462 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-355-33462 → 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/35533462, documented in the API reference.