PERMITS · 778496-99 · DISTRICT 10

Drill: Fullerton Clearfork Unit #7118

Expired

XTO Energy Inc.  ·  Andrews County  · Vertical  · Fullerton field · Final completion

Open the well record →

API 42-003-45955 · everything on file for the well this permit is for

Feb 15, 2014
issued
7,700
permitted depth, ft
42-003-45955
API number
1
version on file

FIRST SEEN BY PETRORA FEB 15, 2014 · WHY THIS DIFFERS FROM THE ISSUE DATE

Permitted field

One field on the W-1

The W-1 names one field, and the well must be completed in it or the operator files again.

FieldFormationProposed wellCompleted in it
Fullerton33230001—OilMay 22, 2014

Lifecycle

  1. Jan 29, 2014Received · Application received by the RRC
  2. Feb 15, 2014Issued · Permit approved
  3. Apr 24, 2014Spud · Drilling began
  4. Apr 27, 2014Surface casing · Surface string set
  5. May 22, 2014Well status · Final completion
  6. Feb 15, 2016Expired · Not drilled within the permit term

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

Surface location

Acres
29,541.59
Nearest town
17.2 mi NW of Andrews
Nearest lease line
6,058 ft

No coordinates yet. The RRC's GIS record usually lands within days of issuance; permits from the historical master file never carry one.

Application records

Status entries the RRC filed against this permit number.

Status no.ReceivedStatusOperatorLease / well
778496-99Jan 29, 2014AXTO Energy Inc.Fullerton Clearfork Unit #7118

Wells nearby

Every well with a location on file around this permit's well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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