PERMITS · 683470-98 · DISTRICT 13

Drill: Weldon Young Unit #8H

Expired

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

Open the well record →

API 42-121-33786 · everything on file for the well this permit is for

Aug 3, 2009
issued
9,000
permitted depth, ft
42-121-33786
API number
2
versions on file

FIRST SEEN BY PETRORA AUG 3, 2009 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Aug 3, 2009Issued · Permit approved
  2. Jul 22, 2010Spud · Drilling began
  3. Jul 23, 2010Surface casing · Surface string set
  4. Aug 6, 2010Well status · Final completion
  5. Dec 15, 2010Received · Application received by the RRC
  6. Dec 23, 2010Amended · Changed after issuance
  7. Aug 3, 2011Expired · Not drilled within the permit term

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

Surface location

Acres
264.07
Nearest town
3.1 mi NW of Ponder
Nearest lease line
332 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 LPDec 15, 2010Aug 3, 2009Dec 23, 20109,000Aug 3, 2009
99DrillBurlington Resources O & G Co LPJul 24, 2009Aug 3, 2009—9,000Aug 3, 2009

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
683470-98Dec 15, 2010ABurlington Resources O & G Co LPWeldon Young Unit #8H
683470-99Jul 24, 2009ABurlington Resources O & G Co LPWeldon Young Unit #8H

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