PERMITS · 660697-98 · DISTRICT 13

Drill: Gage-Pitts Unit #3H

Expired

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

Open the well record →

API 42-497-36529 · everything on file for the well this permit is for

May 15, 2008
issued
9,000
permitted depth, ft
42-497-36529
API number
2
versions on file

FIRST SEEN BY PETRORA MAY 15, 2008 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. May 15, 2008Issued · Permit approved
  2. May 20, 2008Spud · Drilling began
  3. May 21, 2008Surface casing · Surface string set
  4. Jun 7, 2008Well status · Final completion
  5. Nov 10, 2008Received · Application received by the RRC
  6. Dec 18, 2008Amended · Changed after issuance
  7. May 15, 2010Expired · Not drilled within the permit term

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

Surface location

Acres
302.03
Nearest town
7.9 mi NW of Ponder
Nearest lease line
320 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 LPNov 10, 2008May 15, 2008Dec 18, 20089,000May 15, 2008
99DrillBurlington Resources O & G Co LPApr 29, 2008May 15, 2008—9,000May 15, 2008

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
660697-98Nov 10, 2008ABurlington Resources O & G Co LPGage-Pitts Unit #3H
660697-99Apr 29, 2008ABurlington Resources O & G Co LPGage-Pitts Unit #3H

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