PERMITS · 609870-98 · DISTRICT 9

Drill: Shurley 166 #22

Expired

Dominion Oklahoma Texas E&P, Inc  ·  Sutton County  · Vertical  · Side one multi completion

Open the well record →

API 42-435-37703 · everything on file for the well this permit is for

Nov 28, 2005
issued
8,300
permitted depth, ft
42-435-37703
API number
2
versions on file

FIRST SEEN BY PETRORA NOV 28, 2005 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Nov 28, 2005Issued · Permit approved
  2. Aug 8, 2006Spud · Drilling began
  3. Aug 9, 2006Surface casing · Surface string set
  4. Aug 14, 2006Well status · Side one multi completion
  5. May 31, 2007Received · Application received by the RRC
  6. Sep 13, 2007Amended · Changed after issuance
  7. Nov 28, 2007Expired · Not drilled within the permit term

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

Surface location

Acres
640
Nearest town
9 mi SW of Sonora
Nearest lease line
520 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
98DrillDominion Oklahoma Texas E&P, IncMay 31, 2007Nov 28, 2005Sep 13, 20078,300Nov 28, 2005
99DrillDominion Oklahoma Texas E&P, IncNov 21, 2005Nov 28, 2005—7,450Nov 28, 2005

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
609870-98May 31, 2007ADominion Oklahoma Texas E&P, IncShurley 166 #22
609870-99Nov 21, 2005ADominion Oklahoma Texas E&P, IncShurley 166 #22

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