PERMITS · 679752-97 · DISTRICT 13

Drill: Brown F #2

Expired

Texas Energy Operations, LC  ·  Archer County  · Vertical  · Final completion

Mar 30, 2009
issued
9,000
permitted depth, ft
42-009-41988
API number
3
versions on file

FIRST SEEN BY PETRORA MAR 30, 2009 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Mar 30, 2009Issued · Permit approved
  2. May 29, 2009Spud · Drilling began
  3. Jun 1, 2009Surface casing · Surface string set
  4. Mar 22, 2010Received · Application received by the RRC
  5. Mar 29, 2010Amended · Changed after issuance
  6. Jun 18, 2010Well status · Final completion
  7. Mar 30, 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
548
Nearest town
10 mi SE of Holliday
Nearest lease line
1,250 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
97DrillTexas Energy Operations, LCMar 22, 2010Mar 30, 2009Mar 29, 20109,000Mar 30, 2009
98DrillTexas Energy Operations, LCNov 9, 2009Mar 30, 2009Nov 13, 20099,000Mar 30, 2009
99DrillTexas Energy Operations, LCMar 23, 2009Mar 30, 2009—9,000Mar 30, 2009

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
679752-97Mar 22, 2010ATexas Energy Operations, LCBrown F #2
679752-98Nov 9, 2009ATexas Energy Operations, LCBrown F #2
679752-99Mar 23, 2009ATexas Energy Operations, LCBrown F #2

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