PERMITS · 611136-99 · DISTRICT 6

Drill: Johnson, B.L. "E" #6

Expired

Goldston Oil Corporation  ·  Wood County  · Vertical  · Quitman (Eagle Ford) field · Plugged dry hole (P&A)

Open the well record →

API 42-499-32043 · everything on file for the well this permit is for

Jan 11, 2006
issued
4,500
permitted depth, ft
42-499-32043
API number
1
version on file

FIRST SEEN BY PETRORA JAN 11, 2006 · 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 well
Quitman (Eagle Ford)73844235Eagle FordOil

Lifecycle

  1. Dec 16, 2005Received · Application received by the RRC
  2. Jan 11, 2006Issued · Permit approved
  3. Mar 13, 2006Spud · Drilling began
  4. Mar 14, 2006Surface casing · Surface string set
  5. Mar 22, 2006Well status · Plugged dry hole (P&A)
  6. Jan 11, 2008Expired · Not drilled within the permit term

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

Surface location

Acres
40
Nearest town
3.5 mi NW of Quitman
Nearest lease line
207 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
611136-99Dec 16, 2005AGoldston Oil CorporationJohnson, B.L. "E" #6

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