PERMITS · 771103-98 · DISTRICT 2
Drill: Ziegler A #1
ExpiredTrio Consulting & Management,llc · Lavaca County · Vertical · Final completion
- Oct 10, 2013
- issued
- 11,600
- permitted depth, ft
- 42-285-33736
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA OCT 10, 2013 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Oct 10, 2013Issued · Permit approved
- Oct 24, 2013Spud · Drilling began
- Nov 26, 2013Well status · Final completion
- Sep 8, 2014Received · Application received by the RRC
- Sep 26, 2014Amended · Changed after issuance
- Oct 10, 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
- 410.13
- Nearest town
- 4.7 mi SE of Hallettsville
- Nearest lease line
- 471 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 | Trio Consulting & Management,llc | Sep 8, 2014 | Oct 10, 2013 | Sep 26, 2014 | 11,600 | Oct 10, 2013 |
| 99 | Drill | Trio Consulting & Management,llc | Oct 3, 2013 | Oct 10, 2013 | — | 11,600 | Oct 10, 2013 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 771103-98 | Sep 8, 2014 | A | Trio Consulting & Management,llc | Ziegler A #1 |
| 771103-99 | Oct 3, 2013 | A | Trio Consulting & Management,llc | Ziegler A #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/771103, documented in the API reference.