PERMITS · 613318-98 · DISTRICT 3
Drill: Cockburn, H.C. #143
ExpiredKCS Resources, Inc. · Wharton County · Vertical · Final completion
- Jan 31, 2006
- issued
- 7,700
- permitted depth, ft
- 42-481-34821
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA JAN 31, 2006 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Jan 31, 2006Issued · Permit approved
- Feb 14, 2006Spud · Drilling began
- Feb 15, 2006Surface casing · Surface string set
- Feb 27, 2006Well status · Final completion
- Sep 6, 2006Received · Application received by the RRC
- Sep 13, 2006Amended · Changed after issuance
- Jan 31, 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
- 2,510.41
- Nearest town
- 2.5 mi W of Magnet
- Nearest lease line
- 510 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 | KCS Resources, Inc. | Sep 6, 2006 | Jan 31, 2006 | Sep 13, 2006 | 7,700 | Jan 31, 2006 |
| 99 | Drill | KCS Resources, Inc. | Jan 31, 2006 | Jan 31, 2006 | — | 7,700 | Jan 31, 2006 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 613318-98 | Sep 6, 2006 | A | KCS Resources, Inc. | Cockburn, H.C. #143 |
| 613318-99 | Jan 31, 2006 | A | KCS Resources, Inc. | Cockburn, H.C. #143 |
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/613318, documented in the API reference.