PERMITS · 533186-99 · DISTRICT 13

Drill: King #2

Expired

Lane Operating Company  ·  Clay County  · Vertical  · Clay County Regular field · Plugged dry hole (P&A)

Open the well record →

API 42-077-34864 · everything on file for the well this permit is for

Jun 19, 2003
issued
4,100
permitted depth, ft
42-077-34864
API number
1
version on file

FIRST SEEN BY PETRORA JUN 19, 2003 · WHY THIS DIFFERS FROM THE ISSUE DATE

Permitted fields

2 fields on the W-1 · completed in one of them

The field the operator is after is Clay County Regular; the other is the district's wildcat field, the fallback for a zone no field is named for.

FieldFormationProposed well
Wildcat22001 · the district's wildcat fieldAnyOil or gas
Clay County Regular18707001—Oil or gas

Lifecycle

  1. Jun 16, 2003Received · Application received by the RRC
  2. Jun 19, 2003Issued · Permit approved
  3. Jun 25, 2003Spud · Drilling began
  4. Jun 25, 2003Surface casing · Surface string set
  5. Jul 3, 2003Well status · Plugged dry hole (P&A)
  6. Jul 28, 2003Final update · Last change in RRC records
  7. Jun 19, 2005Expired · Not drilled within the permit term

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

Surface location

Acres
200
Nearest town
2.5 mi S of Buffalospring
Nearest lease line
930 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
533186-99Jun 16, 2003ALane Operating CompanyKing #2

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