PERMITS · 763950-98 · DISTRICT 2
Drill: Maraldo a 403 #4
ExpiredBurlington Resources O & G Co LP · DE Witt County · Horizontal · Final completion
- Jul 8, 2013
- issued
- 17,000
- permitted depth, ft
- 42-123-33189
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA JUL 8, 2013 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Jul 8, 2013Issued · Permit approved
- Jul 16, 2013Received · Application received by the RRC
- Jul 17, 2013Amended · Changed after issuance
- Aug 13, 2013Spud · Drilling began
- Oct 5, 2013Well status · Final completion
- Jul 8, 2015Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 704
- Nearest town
- 14.8 mi NW of Cuero
- Nearest lease line
- 275 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 | Burlington Resources O & G Co LP | Jul 16, 2013 | Jul 8, 2013 | Jul 17, 2013 | 17,000 | Jul 8, 2013 |
| 99 | Drill | Burlington Resources O & G Co LP | Jun 4, 2013 | Jul 8, 2013 | — | 17,000 | Jul 8, 2013 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 763950-98 | Jul 16, 2013 | A | Burlington Resources O & G Co LP | Maraldo a 403 #4 |
| 763950-99 | Jun 4, 2013 | A | Burlington Resources O & G Co LP | Maraldo a 403 #4 |
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/763950, documented in the API reference.