PERMITS · 710710-98 · DISTRICT 3
Drill: Pelican #1
ExpiredResaca Resources, L.L.C. · Liberty County · Vertical · Final completion
- Feb 28, 2011
- issued
- 9,650
- permitted depth, ft
- 42-291-32838
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA FEB 28, 2011 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Feb 28, 2011Issued · Permit approved
- Apr 22, 2011Spud · Drilling began
- Apr 24, 2011Surface casing · Surface string set
- May 2, 2011Well status · Final completion
- Sep 20, 2011Received · Application received by the RRC
- Sep 27, 2011Amended · Changed after issuance
- Feb 28, 2013Expired · 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
- 3.4 mi NE of Cleveland
- Nearest lease line
- 935 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 | Resaca Resources, L.L.C. | Sep 20, 2011 | Feb 28, 2011 | Sep 27, 2011 | 9,650 | Feb 28, 2011 |
| 99 | Drill | Resaca Resources, L.L.C. | Feb 21, 2011 | Feb 28, 2011 | — | 9,650 | Feb 28, 2011 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 710710-98 | Sep 20, 2011 | A | Resaca Resources, L.L.C. | Pelican #1 |
| 710710-99 | Feb 21, 2011 | A | Resaca Resources, L.L.C. | Pelican #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/710710, documented in the API reference.