PERMITS · 554976-97 · DISTRICT 6

Drill: Benton "J" #13

Expired

Chinn Exploration Company  ·  Rusk County  · Vertical  · Final completion

Dec 21, 2004
issued
11,000
permitted depth, ft
42-401-33461
API number
3
versions on file

FIRST SEEN BY PETRORA DEC 21, 2004 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Dec 21, 2004Issued · Permit approved
  2. Aug 26, 2005Spud · Drilling began
  3. Aug 27, 2005Surface casing · Surface string set
  4. Sep 16, 2005Well status · Final completion
  5. Mar 8, 2006Received · Application received by the RRC
  6. Mar 28, 2006Amended · Changed after issuance
  7. Dec 21, 2006Expired · Not drilled within the permit term

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

Surface location

Acres
40
Nearest town
3.9 mi W of Henderson
Nearest lease line
545 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
97DrillChinn Exploration CompanyMar 8, 2006Dec 21, 2004Mar 28, 200611,000Dec 21, 2004
98DrillChinn Exploration CompanyAug 16, 2005Dec 21, 2004Aug 17, 200511,000Dec 21, 2004
99DrillChinn Exploration CompanyDec 16, 2004Dec 21, 2004—11,000Dec 21, 2004

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
554976-97Mar 8, 2006AChinn Exploration CompanyBenton "J" #13
554976-98Aug 16, 2005AChinn Exploration CompanyBenton "J" #13
554976-99Dec 16, 2004AChinn Exploration CompanyBenton "J" #13

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