PERMITS · 815438-98 · DISTRICT 10
Drill: Calverely 14-A #1
ExpiredDyad Petroleum Company · Glasscock County · Vertical · Final completion
- May 5, 2016
- issued
- 8,200
- permitted depth, ft
- 42-173-37373
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA MAY 5, 2016 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- May 5, 2016Issued · Permit approved
- May 17, 2016Spud · Drilling began
- May 17, 2016Surface casing · Surface string set
- Jun 7, 2016Received · Application received by the RRC
- Jun 8, 2016Amended · Changed after issuance
- Jun 18, 2016Well status · Final completion
- May 5, 2018Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 160
- Nearest town
- 9 mi NW of Garden City
- Nearest lease line
- 467 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 | Dyad Petroleum Company | Jun 7, 2016 | May 5, 2016 | Jun 8, 2016 | 8,200 | May 5, 2016 |
| 99 | Drill | Dyad Petroleum Company | May 4, 2016 | May 5, 2016 | — | 8,000 | May 5, 2016 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 815438-98 | Jun 7, 2016 | A | Dyad Petroleum Company | Calverely 14-A #1 |
| 815438-99 | May 4, 2016 | A | Dyad Petroleum Company | Calverely 14-A #1 |
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/815438, documented in the API reference.