PERMITS · 297113-99 · DISTRICT 4
Recompletion: Seeligson Unit #0175
ExpiredSun Expl. & Prod. Co.-Corpus · Jim Wells County · Vertical · Seeligson (Zone 20-C-44) field · RE-Enter
API 42-249-02788 · everything on file for the well this permit is for
- Feb 6, 1986
- issued
- 6,250
- permitted depth, ft
- 42-249-02788
- API number
- 1
- version on file
FIRST SEEN BY PETRORA FEB 6, 1986 · WHY THIS DIFFERS FROM THE ISSUE DATE
Permitted fields
2 fields on the W-1 · completed in one of them
The field the operator is after is Seeligson (Zone 20-C-44); the other is the district's wildcat field, the fallback for a zone no field is named for.
| Field | Formation | Proposed well |
|---|---|---|
| Wildcat8001 · the district's wildcat field | Any | Oil or gas |
| Seeligson (Zone 20-C-44)82126415 | — | Oil or gas |
Lifecycle
- Feb 6, 1986Received · Application received by the RRC
- Feb 6, 1986Issued · Permit approved
- Feb 6, 1987Expired · Not drilled within the permit term
A drilling permit is valid for two years from issuance unless extended. How permits work →
Surface location
- Acres
- 18,356
- Nearest town
- 7 mi NNE of Premont
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. | Received | Status | Operator | Lease / well |
|---|---|---|---|---|
| 309305-99 | Feb 6, 1986 | A | Sun Expl. & Prod. Co.-Corpus | Seeligson Unit #0175 |
Wells nearby
Every well with a location on file around this permit's well, in any state, nearest first.
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/297113, documented in the API reference.