WELL · 42-409-32721 · DISTRICT 4
Cable-Garrett #1
San Patricio County · Portland N. (Commonwealth Serie field · Directional
Cable-Garrett #1 (API 42-409-32721) is a plugged well in San Patricio County, plugged April 11, 2019, last operated by Royal Production Company Inc..
The RRC has issued one drilling permit (amended once), issued November 22, 2002, permitted to 11,370 ft.
Operator of record
- Based in
- Corpus Christ, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jan 29, 2026
- Permits on file
- 235
- Phone
- (361) 888-4792
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Royal Production Company Inc. |
| Production reports | Royal Production Company, Inc.through Jan 2019 |
| Latest permit | Royal Production Company, Inc.Nov 22, 2002 |
- 11,370
- total depth, ft
- 2
- permits on file
- Nov 22, 2002
- last permit issued
- Feb 26, 2003
- completed
- 0
- cumulative oil, bbl
- 2.1M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Feb 2003 THROUGH Apr 2019
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Feb 26, 2003
- Shut in
- —
- Plugged
- Apr 11, 2019
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 |
|---|---|---|---|---|---|---|
| Cable-Garrett G-4-193950 | Portland, N. (Commonwealth Serie | Royal Production Company, Inc. | 1 | 0 | 2.1M | Feb 2003 – Apr 2019 |
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.
- 1Royal Production Company, Inc.Mar 2003 → Jan 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 525553-97 | Drill | Royal Production Company, Inc. | Jan 13, 2003 | Nov 22, 2002 | Dec 27, 2002 | 11,370 |
| 525553-99 | Drill | Royal Production Company, Inc. | Nov 15, 2002 | Nov 22, 2002 | — | 11,370 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-193950 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,878 | 10,910 | Perforated |
| 11,014 | 11,026 | Perforated |
| 11,205 | 11,244 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 2,061 | 14.75 | 940 S |
| 7.625 | 10,109 | 9.875 | 735 S |
| 4.5 | 11,448 | 6.5 | 225 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 16, 2003 | Mar 19, 2003 | Yes |
| 00 | Apr 25, 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-409-32721 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-409-32721 → 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/40932721, documented in the API reference.