PERMITS · 771405-98 · DISTRICT 2

Drill: Seidel Unit A #2MW

Expired

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

Open the well record →

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

Oct 22, 2013
issued
14,000
permitted depth, ft
42-123-33362
API number
2
versions on file

FIRST SEEN BY PETRORA OCT 22, 2013 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Oct 22, 2013Issued · Permit approved
  2. Mar 1, 2014Spud · Drilling began
  3. Mar 3, 2014Surface casing · Surface string set
  4. Apr 16, 2014Well status · Final completion
  5. Oct 28, 2014Received · Application received by the RRC
  6. Oct 29, 2014Amended · Changed after issuance
  7. Oct 22, 2015Expired · Not drilled within the permit term

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

Surface location

Acres
701.16
Nearest town
13.6 mi NW of Cuero
Nearest lease line
269 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 LPOct 28, 2014Oct 22, 2013Oct 29, 201414,000Oct 22, 2013
99DrillBurlington Resources O & G Co LPOct 8, 2013Oct 22, 2013—14,000Oct 22, 2013

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
771405-98Oct 28, 2014ABurlington Resources O & G Co LPSeidel Unit A #2MW
771405-99Oct 8, 2013ABurlington Resources O & G Co LPSeidel Unit A #2MW

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