PERMITS · 694220-97 · DISTRICT 2

Drill: Davenport #1

Expired

Double Play Oil & Gas, Inc  ·  Karnes County  · Vertical  · Final completion

Apr 12, 2010
issued
4,991
permitted depth, ft
42-255-31663
API number
3
versions on file

FIRST SEEN BY PETRORA APR 12, 2010 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

  1. Apr 12, 2010Issued · Permit approved
  2. May 11, 2010Spud · Drilling began
  3. May 12, 2010Surface casing · Surface string set
  4. May 19, 2010Well status · Final completion
  5. Aug 26, 2010Received · Application received by the RRC
  6. Sep 10, 2010Amended · Changed after issuance
  7. Apr 12, 2012Expired · Not drilled within the permit term

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

Surface location

Acres
100
Nearest town
2.6 mi NW of Charco
Nearest lease line
468 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
97DrillDouble Play Oil & Gas, IncAug 26, 2010Apr 12, 2010Sep 10, 20104,991Apr 12, 2010
98DrillDouble Play Oil & Gas, IncAug 18, 2010Apr 12, 2010Aug 19, 20104,991Apr 12, 2010
99DrillDouble Play Oil & Gas, IncApr 12, 2010Apr 12, 2010—5,000Apr 12, 2010

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
694220-97Aug 26, 2010ADouble Play Oil & Gas, IncDavenport #1
694220-98Aug 18, 2010ADouble Play Oil & Gas, IncDavenport #1
694220-99Apr 12, 2010ADouble Play Oil & Gas, IncDavenport #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/694220, documented in the API reference.