PERMITS · 733149-97 · DISTRICT 2

Drill: Motl Unit A #1

Expired

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

Feb 15, 2012
issued
17,000
permitted depth, ft
42-123-32703
API number
3
versions on file

FIRST SEEN BY PETRORA FEB 15, 2012 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Feb 15, 2012Issued · Permit approved
  2. Apr 1, 2012Spud · Drilling began
  3. Apr 29, 2012Well status · Final completion
  4. Dec 5, 2012Received · Application received by the RRC
  5. Dec 11, 2012Amended · Changed after issuance
  6. Feb 15, 2014Expired · Not drilled within the permit term

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

Surface location

Acres
527.86
Nearest town
8.4 mi NW of Cuero
Nearest lease line
543 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
97DrillBurlington Resources O & G Co LPDec 5, 2012Feb 15, 2012Dec 11, 201217,000Feb 15, 2012
98DrillBurlington Resources O & G Co LPMar 12, 2012Feb 15, 2012Mar 24, 201213,500Feb 15, 2012
99DrillBurlington Resources O & G Co LPFeb 3, 2012Feb 15, 2012—13,500Feb 15, 2012

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
733149-97Dec 5, 2012ABurlington Resources O & G Co LPMotl Unit A #1
733149-98Mar 12, 2012ABurlington Resources O & G Co LPMotl Unit A #1
733149-99Feb 3, 2012ABurlington Resources O & G Co LPMotl Unit A #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/733149, documented in the API reference.