TEXAS · WELLS · CROCKETT COUNTY · SHANNON ESTATE 01-21 LEASE · API 42-105-41310 · DISTRICT 6E
Shannon Estate 01-21 #01
Crockett County · Wildcat field · Vertical
Shannon Estate 01-21 #01 (API 42-105-41310) is a plugged well in Crockett County, plugged December 2, 2016, last operated by Devon Energy Production CO L.P..
The RRC has issued one drilling permit, issued August 1, 2011, permitted to 8,500 ft.
It was permitted by Forest Oil Corporation and has since transferred to Devon Energy Production CO L.P. on the wellbore schedule.
Operator of record
Devon Energy Production Co L.P.
Permitted by Forest Oil Corporation; the EWA schedule now lists a different operator.
- Based in
- Oklahoma City, OK
- P-5 status
- Active (A)
- P-5 last filed
- Dec 18, 2025
- Permits on file
- 9,266
- Phone
- (405) 235-3611
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Devon Energy Production Co L.P. |
| Production reports | none |
| Latest permit | Forest Oil CorporationAug 1, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,500
- total depth, ft
- 1
- permits on file
- Aug 1, 2011
- last permit issued
- Nov 6, 2011
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2011 THROUGH Jan 2017
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 6, 2011
- Shut in
- —
- Plugged
- Dec 2, 2016
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; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Shannon Estate 01-21 O-9-17907 | Wildcat | Devon Energy Production Co, L.P. | 2 | 0 | 0 | Nov 2011 – Jan 2017 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 721077-99 | Drill | Forest Oil Corporation | Jul 27, 2011 | Aug 1, 2011 | Oct 6, 2011 | 8,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Nov 6, 2011 | Shannon Estate 01-21 O-9-17907 | Wildcat | Devon Energy Production Co L.P. | Plugged | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 633 | 17.5 | 515 S |
| 9.625 | 3,200 | 12.25 | 320 S |
| 5.5 | 8,016 | 8.75 | 1,150 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 29, 2013 | Jun 27, 2012 | Yes |
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-105-41310 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-105-41310 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/10541310, documented in the API reference.