PERMITS · 740504-98 · DISTRICT 2

Drill: Koopmann (Allocation) #1

Expired

Burlington Resources O & G Co LP  ·  De Witt County  · Horizontal  · Final completion

Open the well record →

API 42-123-32788 · everything on file for the well this permit is for

May 22, 2012
issued
14,200
permitted depth, ft
42-123-32788
API number
2
versions on file

FIRST SEEN BY PETRORA MAY 22, 2012 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. May 22, 2012Issued · Permit approved
  2. Nov 1, 2013Spud · Drilling began
  3. Nov 3, 2013Surface casing · Surface string set
  4. Jan 8, 2014Well status · Final completion
  5. May 15, 2014Received · Application received by the RRC
  6. May 22, 2014Expired · Not drilled within the permit term
  7. Jul 9, 2014Amended · Changed after issuance

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

Surface location

Acres
936
Nearest town
7.6 mi N of Yorktown
Nearest lease line
1 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
98DrillBurlington Resources O & G Co LPMay 15, 2014May 22, 2012Jul 9, 201414,200May 22, 2012
99DrillBurlington Resources O & G Co LPMay 11, 2012May 22, 2012—14,200May 22, 2012

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
740504-98May 15, 2014ABurlington Resources O & G Co LPKoopmann (Allocation) #1
740504-99May 11, 2012ABurlington Resources O & G Co LPHilmer Koopman Unit a 274 #2

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