PERMITS · 502739-98 · DISTRICT 2
Drill: Wood "E" #74
ExpiredCharro Operating, L.L.C. · Goliad County · Vertical · Final completion
- Dec 7, 2000
- issued
- 5,300
- permitted depth, ft
- 42-175-33309
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA DEC 7, 2000 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Dec 7, 2000Issued · Permit approved
- Dec 13, 2000Spud · Drilling began
- Dec 18, 2000Well status · Final completion
- Sep 19, 2002Received · Application received by the RRC
- Sep 19, 2002Amended · Changed after issuance
- Jan 7, 2003Final update · Last change in RRC records
- Sep 19, 2004Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 5,458.95
- Nearest town
- 12 mi S of Goliad
- Nearest lease line
- 0 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 | Charro Operating, L.L.C. | Sep 19, 2002 | Dec 7, 2000 | Sep 19, 2002 | 5,300 | Dec 7, 2000 |
| 99 | Drill | Charro Operating, L.L.C. | Dec 7, 2000 | Dec 7, 2000 | — | 5,300 | Dec 7, 2000 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 502739-98 | Sep 19, 2002 | A | Charro Operating, L.L.C. | Wood "E" #74 |
| 502739-99 | Dec 7, 2000 | A | Charro Operating, L.L.C. | Wood "E" #74 |
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/502739, documented in the API reference.