PERMITS · 544702-98 · DISTRICT 14
Recompletion: Lynn #1050
ExpiredLatigo Petroleum Texas, LP · Ochiltree County · Vertical · Side one multi completion
- Apr 21, 2004
- issued
- 8,504
- permitted depth, ft
- 42-357-30398
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA APR 21, 2004 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Apr 21, 2004Issued · Permit approved
- Feb 22, 2005Spud · Drilling began
- Mar 15, 2005Well status · Side one multi completion
- Apr 21, 2006Expired · Not drilled within the permit term
- Apr 25, 2006Received · Application received by the RRC
- Apr 25, 2006Amended · Changed after issuance
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 640
- Nearest town
- 4 mi E of Spearman
- Nearest lease line
- 1,250 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 | Recompletion | Latigo Petroleum Texas, LP | Apr 25, 2006 | Apr 21, 2004 | Apr 25, 2006 | 8,504 | Apr 21, 2004 |
| 99 | Recompletion | Latigo Petroleum Texas, LP | Apr 20, 2004 | Apr 21, 2004 | — | 8,504 | Apr 21, 2004 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 544702-98 | Apr 25, 2006 | A | Latigo Petroleum Texas, LP | Lynn #1050 |
| 544702-99 | Apr 20, 2004 | A | Latigo Petroleum Texas, LP | Lynn #1050 |
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/544702, documented in the API reference.