PERMITS · 622403-98 · DISTRICT 10
Drill: West Ranch South #6901A
ExpiredRiata Energy, Inc. · Pecos County · Vertical · Final completion
- Jul 12, 2006
- issued
- 11,000
- permitted depth, ft
- 42-371-37758
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA JUL 12, 2006 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Jul 12, 2006Issued · Permit approved
- Jul 14, 2006Spud · Drilling began
- Jul 23, 2006Surface casing · Surface string set
- Sep 26, 2006Received · Application received by the RRC
- Sep 27, 2006Amended · Changed after issuance
- Nov 25, 2006Well status · Final completion
- Jul 12, 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
- 9,920
- Nearest town
- 35 mi SE of FT Stockton
- Nearest lease line
- 6,089 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 | Riata Energy, Inc. | Sep 26, 2006 | Jul 12, 2006 | Sep 27, 2006 | 11,000 | Jul 12, 2006 |
| 99 | Drill | Riata Energy, Inc. | Jul 11, 2006 | Jul 12, 2006 | — | 9,000 | Jul 12, 2006 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 622403-98 | Sep 26, 2006 | A | Riata Energy, Inc. | West Ranch South #6901A |
| 622403-99 | Jul 11, 2006 | A | Riata Energy, Inc. | West Ranch South #6901A |
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/622403, documented in the API reference.