PERMITS · 614722-98 · DISTRICT 2
Drill: Shelton #2
ExpiredCorum Production Company · Victoria County · Vertical · Final completion
- Feb 27, 2006
- issued
- 4,500
- permitted depth, ft
- 42-469-33968
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA FEB 27, 2006 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Feb 27, 2006Issued · Permit approved
- Mar 12, 2006Spud · Drilling began
- Mar 14, 2006Surface casing · Surface string set
- Mar 19, 2006Well status · Final completion
- Oct 20, 2006Received · Application received by the RRC
- Oct 27, 2006Amended · Changed after issuance
- Feb 27, 2008Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 105.2
- Nearest town
- 4 mi SE of Dacosta
- Nearest lease line
- 619 ft
No coordinates yet. The RRC's GIS record usually lands within days of issuance; permits from the historical master file never carry one.
Versions
The RRC numbers versions down from 99: 99 is the original filing, 98 the first amendment. Current version first.
| Seq | Type | Operator | Received | Issued | Amended | Depth | Seen |
|---|---|---|---|---|---|---|---|
| 98 | Drill | Corum Production Company | Oct 20, 2006 | Feb 27, 2006 | Oct 27, 2006 | 4,500 | Feb 27, 2006 |
| 99 | Drill | Corum Production Company | Feb 22, 2006 | Feb 27, 2006 | — | 4,500 | Feb 27, 2006 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 614722-98 | Oct 20, 2006 | A | Corum Production Company | Shelton #2 |
| 614722-99 | Feb 22, 2006 | A | Corum Production Company | Shelton #2 |
About this data
W-1 drilling permit from the RRC OGA049M master and daily daf420 files, refreshed every business day. Surface coordinates come from the daily file only. Amendments appear as sequence numbers on the same permit; the lowest is current.
Developers: this page as JSON is GET /v1/data/permits/tx/614722, documented in the API reference.