PERMITS · 684607-98 · DISTRICT 1
Drill: Cage Ranch #326H
ExpiredTxco Resources Inc. · Maverick County · Horizontal · Final completion
- Sep 10, 2009
- issued
- 6,850
- permitted depth, ft
- 42-323-33333
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA SEP 10, 2009 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Sep 10, 2009Issued · Permit approved
- Sep 12, 2009Spud · Drilling began
- Sep 12, 2009Surface casing · Surface string set
- Oct 7, 2009Well status · Final completion
- Oct 22, 2009Received · Application received by the RRC
- Oct 28, 2009Amended · Changed after issuance
- Sep 10, 2011Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 24,979.67
- Nearest town
- 5.7 mi E of EL Indio
- Nearest lease line
- 299 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 | Txco Resources Inc. | Oct 22, 2009 | Sep 10, 2009 | Oct 28, 2009 | 6,850 | Sep 10, 2009 |
| 99 | Drill | Txco Resources Inc. | Aug 28, 2009 | Sep 10, 2009 | — | 7,030 | Sep 10, 2009 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 684607-98 | Oct 22, 2009 | A | Txco Resources Inc. | Cage Ranch #326H |
| 684607-99 | Aug 28, 2009 | A | Txco Resources Inc. | Cage Ranch #326H |
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/684607, documented in the API reference.