PERMITS · 671407-98 · DISTRICT 1
Drill: Cage-Briscoe B #236H
ExpiredTxco Resources Inc. · Maverick County · Horizontal · Final completion
- Oct 3, 2008
- issued
- 7,000
- permitted depth, ft
- 42-323-33217
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA OCT 3, 2008 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Oct 3, 2008Issued · Permit approved
- Oct 16, 2008Spud · Drilling began
- Oct 16, 2008Surface casing · Surface string set
- Dec 11, 2008Well status · Final completion
- Jan 12, 2009Received · Application received by the RRC
- Feb 10, 2009Amended · Changed after issuance
- Oct 3, 2010Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 7,014.61
- Nearest town
- 4 mi E of EL Indio
- Nearest lease line
- 48 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. | Jan 12, 2009 | Oct 3, 2008 | Feb 10, 2009 | 7,000 | Oct 3, 2008 |
| 99 | Drill | Txco Resources Inc. | Sep 18, 2008 | Oct 3, 2008 | — | 7,000 | Oct 3, 2008 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 671407-98 | Jan 12, 2009 | A | Txco Resources Inc. | Cage-Briscoe B #236H |
| 671407-99 | Sep 18, 2008 | A | Txco Resources Inc. | Cage-Briscoe B #236H |
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/671407, documented in the API reference.