PERMITS · 602152-97 · DISTRICT 14
Drill: Schultz 696 #3
ExpiredEOG Resources, Inc. · Lipscomb County · Vertical
- Jun 17, 2005
- issued
- 10,000
- permitted depth, ft
- 42-295-32897
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA JUN 17, 2005 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Jun 17, 2005Issued · Permit approved
- Jun 25, 2005Spud · Drilling began
- Jun 26, 2005Surface casing · Surface string set
- Jul 19, 2005Received · Application received by the RRC
- Jul 19, 2005Amended · Changed after issuance
- Jun 17, 2007Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 624
- Nearest town
- 4.5 mi NE of Lipscomb
- Nearest lease line
- 660 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 |
|---|---|---|---|---|---|---|---|
| 97 | Drill | EOG Resources, Inc. | Jul 19, 2005 | Jun 17, 2005 | Jul 19, 2005 | 10,000 | Jun 17, 2005 |
| 99 | Drill | EOG Resources, Inc. | Jun 16, 2005 | Jun 17, 2005 | — | 10,000 | Jun 17, 2005 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 602152-97 | Jul 19, 2005 | A | EOG Resources, Inc. | Schultz 696 #3 |
| 602152-98 | Jun 17, 2005 | Z | EOG Resources, Inc. | Schultz 696 #3 |
| 602152-99 | Jun 16, 2005 | A | EOG Resources, Inc. | Schultz 696 #3 |
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/602152, documented in the API reference.