PERMITS · 787393-98 · DISTRICT 6
Drill: Bice #1
ExpiredBuffco Production Inc. · Cherokee County · Vertical · Final completion
- Jun 30, 2014
- issued
- 10,900
- permitted depth, ft
- 42-073-31517
- API number
- 2
- versions on file
FIRST SEEN BY PETRORA JUN 30, 2014 · WHY THIS DIFFERS FROM THE ISSUE DATE
Lifecycle
- Jun 30, 2014Issued · Permit approved
- Aug 16, 2014Spud · Drilling began
- Aug 17, 2014Surface casing · Surface string set
- Aug 29, 2014Well status · Final completion
- Oct 13, 2014Received · Application received by the RRC
- Oct 14, 2014Amended · Changed after issuance
- Jun 30, 2016Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 699.69
- Nearest town
- 3 mi N of Alto, TX
- Nearest lease line
- 1,872 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 | Buffco Production Inc. | Oct 13, 2014 | Jun 30, 2014 | Oct 14, 2014 | 10,900 | Jun 30, 2014 |
| 99 | Drill | East Texas Energy Corporation | May 19, 2014 | Jun 30, 2014 | — | 10,900 | Jun 30, 2014 |
Application records
Status entries the RRC filed against this permit number.
| Status no. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 787393-98 | Oct 13, 2014 | A | Buffco Production Inc. | Bice #1 |
| 787393-99 | May 19, 2014 | A | East Texas Energy Corporation | Bice #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/787393, documented in the API reference.