PERMITS · 726489-99 · DISTRICT 2

Drill: Schlenker Unit A #1

Expired

Burlington Resources O & G Co LP  ·  De Witt County  · Horizontal  · Eagleville (Eagle Ford-2) field · Final completion

Open the well record →

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

Oct 21, 2011
issued
12,800
permitted depth, ft
42-123-32626
API number
1
version on file

FIRST SEEN BY PETRORA OCT 21, 2011 · WHY THIS DIFFERS FROM THE ISSUE DATE

Permitted field

One field on the W-1

The W-1 names one field, and the well must be completed in it or the operator files again.

FieldFormationProposed wellCompleted in it
Eagleville (Eagle Ford-2)27135750Eagle Ford 2Oil or gasApr 8, 2012

Lifecycle

  1. Oct 18, 2011Received · Application received by the RRC
  2. Oct 21, 2011Issued · Permit approved
  3. Mar 3, 2012Spud · Drilling began
  4. Apr 8, 2012Well status · Final completion
  5. Oct 21, 2013Expired · Not drilled within the permit term

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

Surface location

Acres
278.74
Nearest town
14.2 mi NW of Cuero
Nearest lease line
290 ft

No coordinates yet. The RRC's GIS record usually lands within days of issuance; permits from the historical master file never carry one.

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
726489-99Oct 18, 2011ABurlington Resources O & G Co LPSchlenker Unit A #1

Wells nearby

Every well with a location on file around this permit's well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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