PERMITS · 555888-97 · DISTRICT 4

Drill: Simpson, June Shallow GU #1

Expired

EOG Resources, Inc.  ·  Nueces County  · Directional  · Final completion

Jan 7, 2005
issued
17,500
permitted depth, ft
42-355-33694
API number
3
versions on file

FIRST SEEN BY PETRORA JAN 7, 2005 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Jan 7, 2005Issued · Permit approved
  2. Feb 1, 2005Spud · Drilling began
  3. Feb 3, 2005Surface casing · Surface string set
  4. Mar 20, 2005Well status · Final completion
  5. May 20, 2005Received · Application received by the RRC
  6. May 20, 2005Amended · Changed after issuance
  7. Jan 7, 2007Expired · Not drilled within the permit term

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

Surface location

Acres
240
Nearest town
7 mi W of Corpus Christ
Nearest lease line
846 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
97DrillEOG Resources, Inc.May 20, 2005Jan 7, 2005May 20, 200517,500Jan 7, 2005
98DrillEOG Resources, Inc.Feb 24, 2005Jan 7, 2005Feb 24, 200517,500Jan 7, 2005
99DrillVentex Operating Corp.Jan 7, 2005Jan 7, 2005—11,100Jan 7, 2005

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
555888-97May 20, 2005AEOG Resources, Inc.Simpson, June Shallow GU #1
555888-98Feb 24, 2005AEOG Resources, Inc.Simpson, June Deep FU #1
555888-99Jan 7, 2005AVentex Operating Corp.West Oso Unit #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/555888, documented in the API reference.