PERMITS · 404221-98 · DISTRICT 3

Recompletion: Yegua Unit #H 1

Expired

Union Pacific Resources Company  ·  Burleson County  · Horizontal · Sidetrack  · Final completion

Open the well record →

API 42-051-33273 · everything on file for the well this permit is for

Oct 12, 1992
issued
14,900
permitted depth, ft
42-051-33273
API number
2
versions on file

FIRST SEEN BY PETRORA OCT 12, 1992 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Oct 12, 1992Issued · Permit approved
  2. Jan 21, 1993Received · Application received by the RRC
  3. Jan 25, 1993Amended · Changed after issuance
  4. Jan 25, 1993Spud · Drilling began
  5. Feb 9, 1993Well status · Final completion
  6. Apr 16, 1993Final update · Last change in RRC records
  7. Jan 25, 1995Expired · Not drilled within the permit term

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

Surface location

Acres
360
Nearest town
6.4 mi E of Somerville

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
98RecompletionUnion Pacific Resources CompanyJan 21, 1993Oct 12, 1992Jan 25, 199314,900Oct 12, 1992
99RecompletionUnion Pacific Resources CompanyOct 2, 1992Oct 12, 1992—14,900Oct 12, 1992

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
404221-98Jan 21, 1993AUnion Pacific Resources CompanyYegua Unit #H 1
404221-99Oct 2, 1992AUnion Pacific Resources CompanyYegua Unit #H 1

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