PERMITS · 803479-98 · DISTRICT 10

Drill: State Chevyhaftun 56-T2-10X15 SA #1H

Expired

BHP Billiton Pet(txla OP) Co  ·  Reeves County  · Horizontal  · Final completion

Open the well record →

API 42-389-34767 · everything on file for the well this permit is for

Feb 6, 2015
issued
12,500
permitted depth, ft
42-389-34767
API number
2
versions on file

FIRST SEEN BY PETRORA FEB 6, 2015 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Feb 6, 2015Issued · Permit approved
  2. Feb 19, 2015Spud · Drilling began
  3. Feb 20, 2015Surface casing · Surface string set
  4. Jul 3, 2015Well status · Final completion
  5. Aug 4, 2015Received · Application received by the RRC
  6. Aug 19, 2015Amended · Changed after issuance
  7. Feb 6, 2017Expired · Not drilled within the permit term

A drilling permit is valid for two years from issuance unless extended. How permits work →

Surface location

Acres
966.08
Nearest town
4.4 mi NE of Orla
Nearest lease line
200 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.

SeqTypeOperatorReceivedIssuedAmendedDepthSeen
98DrillBHP Billiton Pet(txla OP) CoAug 4, 2015Feb 6, 2015Aug 19, 201512,500Feb 6, 2015
99DrillBHP Billiton Pet(txla OP) CoFeb 3, 2015Feb 6, 2015—12,500Feb 6, 2015

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
803479-98Aug 4, 2015ABHP Billiton Pet(txla OP) CoState Chevyhaftun 56-T2-10X15 SA #1H
803479-99Feb 3, 2015ABHP Billiton Pet(txla OP) CoState Tunstill 56-T2-10 #2H

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/803479, documented in the API reference.