PERMITS · 676347-99 · DISTRICT 13

Drill: Brown A #3

Expired

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

Open the well record →

API 42-009-41945 · everything on file for the well this permit is for

Jan 6, 2009
issued
9,000
permitted depth, ft
42-009-41945
API number
1
version on file

FIRST SEEN BY PETRORA JAN 6, 2009 · WHY THIS DIFFERS FROM THE ISSUE DATE

Permitted field

One field on the W-1

The W-1 names one field, and the well must be completed in it or the operator files again.

FieldFormationProposed wellCompleted in it
Archer County Regular3446001—Oil or gasFeb 18, 2010

Lifecycle

  1. Dec 15, 2008Received · Application received by the RRC
  2. Jan 6, 2009Issued · Permit approved
  3. Mar 30, 2009Spud · Drilling began
  4. Mar 30, 2009Surface casing · Surface string set
  5. Feb 18, 2010Well status · Final completion
  6. Jan 6, 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
160
Nearest town
10 mi SE of Holliday
Nearest lease line
467 ft

No coordinates yet. The RRC's GIS record usually lands within days of issuance; permits from the historical master file never carry one.

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
676347-99Dec 15, 2008ATexas Energy Operations, LCBrown A #3

Wells nearby

Every well with a location on file around this permit's well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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