PERMITS · 448173-99 · DISTRICT 1

Drill: SBR #71

Expired

Swift Energy Company  ·  McMullen County  · Vertical  · A.W.P. (Olmos) field · Final completion

Open the well record →

API 42-311-33193 · everything on file for the well this permit is for

May 15, 1996
issued
11,000
permitted depth, ft
42-311-33193
API number
1
version on file

FIRST SEEN BY PETRORA MAY 15, 1996 · 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
A.W.P. (Olmos)256500OlmosGasJun 30, 1906

Lifecycle

  1. May 15, 1996Received · Application received by the RRC
  2. May 15, 1996Issued · Permit approved
  3. Jun 19, 1996Spud · Drilling began
  4. Jun 20, 1996Surface casing · Surface string set
  5. Jun 30, 1996Well status · Final completion
  6. Aug 15, 1996Final update · Last change in RRC records
  7. May 15, 1998Expired · Not drilled within the permit term

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

Surface location

Acres
161
Nearest town
5.5 mi SE of Tilden

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
448173-99May 15, 1996ASwift Energy CompanySBR #71

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