PERMITS · 732054-97 · DISTRICT 10

Drill: Evans #8

Expired

Bluestem Energy Holdings, LLC  ·  Midland County  · Vertical  · Final completion

Mar 6, 2012
issued
11,500
permitted depth, ft
42-329-37899
API number
3
versions on file

FIRST SEEN BY PETRORA MAR 6, 2012 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Mar 6, 2012Issued · Permit approved
  2. May 26, 2012Spud · Drilling began
  3. May 26, 2012Surface casing · Surface string set
  4. Jun 9, 2012Well status · Final completion
  5. Sep 28, 2012Received · Application received by the RRC
  6. Oct 15, 2012Amended · Changed after issuance
  7. Mar 6, 2014Expired · Not drilled within the permit term

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

Surface location

Acres
320
Nearest town
17.6 mi E of Midland
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.

Versions

The RRC numbers versions down from 99: 99 is the original filing, 98 the first amendment. Current version first.

SeqTypeOperatorReceivedIssuedAmendedDepthSeen
97DrillBluestem Energy Holdings, LLCSep 28, 2012Mar 6, 2012Oct 15, 201211,500Mar 6, 2012
98DrillBluestem Energy Holdings, LLCApr 26, 2012Mar 6, 2012May 11, 201211,500Mar 6, 2012
99DrillBluestem Energy Holdings, LLCJan 19, 2012Mar 6, 2012—10,500Mar 6, 2012

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
732054-97Sep 28, 2012ABluestem Energy Holdings, LLCEvans #8
732054-98Apr 26, 2012ABluestem Energy Holdings, LLCEvans #8
732054-99Jan 19, 2012ABluestem Energy Holdings, LLCEvans #8

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