TEXAS · WELLS · ARANSAS COUNTY · API 42-007-00259 · DISTRICT 04

State Tract 81 #1

Plugged

Aransas County · Goose Island (7100 -B-) field  · Vertical

State Tract 81 #1 (API 42-007-00259) is a plugged well in Aransas County, plugged June 23, 1995, last operated by Hunt Oil Company.

The RRC has issued 2 drilling permits between 1980 and 1992, permitted to 8,505 ft.

Completion filings report one formation top, including Frio.

Operator of record

Hunt Oil Company

Based in
Dallas, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 20, 2026
Permits on file
1,472
Phone
(214) 978-8000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHunt Oil Company
Production reportsHunt Oil Companythrough May 1994
Latest permitHunt Oil CompanyMar 18, 1992
8,505
total depth, ft
2
permits on file
Mar 18, 1992
last permit issued
Apr 12, 1992
completed
0
cumulative oil, bbl
74K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 12, 1992
Shut in
—
Plugged
Jun 23, 1995

Surface location

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

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Tract 81 O-4-9550Goose Island (C SD, Lo.)Hunt Oil Company100Jan 1993 – Oct 1995
State Tract 81 G-4-141417Goose Island (7100 -B-)Hunt Oil Company1074KJan 1993 – Sep 1995

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Hunt Oil CompanyJan 1993 → May 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
397353-99RecompletionHunt Oil CompanyMar 17, 1992Mar 18, 1992Apr 3, 19928,505
74366-99OtherHunt Oil CompanyMar 6, 1980Mar 6, 1980—8,505

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 12, 1992State Tract 81 G-4-141417Goose Island (7100 -B-)Hunt Oil CompanyPlugged—
May 7, 1980State Tract 81 O-4-9550Goose Island (C SD Lo.)Hunt Oil CompanyPlugged—
Sep 1, 1952State Tract 81 G-4-10595Goose Island (7100 -B-)Hunt Oil CompanyPlugged—
—State Tract 81 G-4-60666Goose Island (7100 -C-)Hunt Oil CompanyPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 22 ft elevation.Download CSV →

FormationMD ftSubsea
Frio6,700-6,678

Perforations

Perforated and open-hole intervals.

FromToType
6,9686,988Perforated
7,0017,014Perforated
7,0907,104Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
16105—350 S
10.751,02815700 S
2.56,994——
2.3757,088——
77,3599.625400 S
77,3599.875400 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 16, 1992Apr 23, 1992Yes
00Jun 4, 1992——
00Jan 12, 1984May 13, 1980—
00Jan 12, 1984Jan 10, 1975—
00Jan 12, 1984——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/00700259, documented in the API reference.