PERMITS · 223816-99 · DISTRICT 3

Drill: El Campo Well Service, Inc. #1

Expired

Richards Producing Company  ·  Wharton County  · Vertical  · RE-Enter · Plugged dry hole (P&A)

Open the well record →

API 42-481-32612 · everything on file for the well this permit is for

Dec 15, 1983
issued
6,800
permitted depth, ft
42-481-32612
API number
1
version on file

FIRST SEEN BY PETRORA DEC 15, 1983 · 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 well
Wildcat6001 · the district's wildcat fieldAnyOil or gas

Lifecycle

  1. Dec 13, 1983Received · Application received by the RRC
  2. Dec 15, 1983Issued · Permit approved
  3. Jan 15, 1984Spud · Drilling began
  4. Jan 22, 1984Well status · Plugged dry hole (P&A)
  5. Apr 25, 1984Final update · Last change in RRC records
  6. Dec 15, 1984Expired · Not drilled within the permit term

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

Surface location

Acres
224
Nearest town
5 mi E of Pierce

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
224916-99Dec 13, 1983ARichards Producing CompanyEl Campo Well Service, Inc. #1

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