PERMITS · 545197-98 · DISTRICT 3
Drill: 1966 Partnership #6
ExpiredTriple "B" Production Drlg Inc · Trinity County · Vertical · Final completion
- May 26, 2004
- issued
- 2,000
- permitted depth, ft
- 42-455-30481
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA MAY 26, 2004 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- May 26, 2004Issued · Permit approved
- May 18, 2005Received · Application received by the RRC
- May 20, 2005Amended · Changed after issuance
- Aug 2, 2005Spud · Drilling began
- Aug 5, 2005Well status · Final completion
- May 26, 2006Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 177
- Nearest town
- 1 mi SW of Gaston
- Nearest lease line
- 150 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 | Triple "B" Production Drlg Inc | May 18, 2005 | May 26, 2004 | May 20, 2005 | 2,000 | May 26, 2004 |
| 99 | Drill | Triple "B" Production Drlg Inc | Apr 30, 2004 | May 26, 2004 | — | 2,000 | May 26, 2004 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 545197-98 | May 18, 2005 | A | Triple "B" Production Drlg Inc | 1966 Partnership #6 |
| 545197-99 | Apr 30, 2004 | A | Triple "B" Production Drlg Inc | 1966 Partnership #6 |
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/545197, documented in the API reference.