PERMITS · 480402-97 · DISTRICT 14

Recompletion: Parker, Clarence Henry "a" 618 #1

Expired

Crescendo Resources, L.P.  ·  Lipscomb County  · Vertical  · Final completion

Oct 30, 1998
issued
10,158
permitted depth, ft
42-295-31100
API number
2
versions on file

FIRST SEEN BY PETRORA OCT 30, 1998 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. May 18, 1998Spud · Drilling began
  2. Jun 17, 1998Well status · Final completion
  3. Oct 30, 1998Issued · Permit approved
  4. Mar 3, 1999Received · Application received by the RRC
  5. Mar 9, 1999Amended · Changed after issuance
  6. Mar 19, 1999Final update · Last change in RRC records
  7. Mar 9, 2001Expired · Not drilled within the permit term

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

Surface location

Acres
644
Nearest town
14 mi E of Lipscomb
Nearest lease line
0 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
97RecompletionCrescendo Resources, L.P.Mar 3, 1999Oct 30, 1998Mar 9, 199910,158Oct 30, 1998
99RecompletionCrescendo Resources, L.P.Oct 23, 1998Oct 30, 1998—10,158Oct 30, 1998

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
480402-97Mar 3, 1999ACrescendo Resources, L.P.Parker, Clarence Henry "a" 618 #1
480402-98Feb 11, 1999PCrescendo Resources, L.P.Parker, Clarence Henry "a" 618 #1
480402-99Oct 23, 1998ACrescendo Resources, L.P.Parker, Clarence Henry "a" 618 #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/480402, documented in the API reference.