WELL · 42-325-30804 · DISTRICT 1

State Wilson Unit #3X

Plugged

Medina County · Taylor-Ina field  · Vertical

State Wilson Unit #3X (API 42-325-30804) is a plugged well in Medina County, plugged July 20, 2001, last operated by Wetzel Oil Company.

The RRC has issued one drilling permit, issued October 17, 1977, permitted to 1,000 ft.

It was permitted by Petro Oil & Gas, Inc. and has since transferred to Wetzel Oil Company on the wellbore schedule.

Its 2 leases have reported 160K barrels of oil and 53 mcf of gas since January 1993, last reporting in July 2026. The leases carry 156 wells, so these are lease totals, not this well alone.

Operator of record

Wetzel Oil Company

Permitted by Petro Oil & Gas, Inc.; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed Feb 8, 2008

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWetzel Oil Company
Production reportsBurnett Oil Co., Inc.through Apr 2026
Latest permitPetro Oil & Gas, Inc.Oct 17, 1977

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

1,000
total depth, ft
1
permits on file
Oct 17, 1977
last permit issued
Apr 27, 1978
completed
160K
cumulative oil, bbl
53
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 27, 1978
Shut in
—
Plugged
Jul 20, 2001

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 156 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Middleton Petroleum O-1-3335Taylor-InaBurnett Oil Co., Inc.147159K27Jan 1993 – Jul 2026
State Wilson Unit O-1-5737Taylor-InaWetzel Oil Company91.09K26Jan 1993 – Feb 1997

Oil, barrels lease total

Last 12 months 696 · prior 12 1,440(-52%)

0200400202420252026

Chain of custody

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

  1. 1Jenex Operating Company of TexasJan 1993 → Sep 1993
  2. 2Production Resources, Inc.Oct 1993 → Apr 1995
  3. 3Wetzel Oil CompanyMay 1995 → May 2007
  4. 4Middleton Petroleum LLCJun 2007 → Feb 2017
  5. 5Tehuacana Crude Oil, LLCMar 2017 → Jan 2022
  6. 6Burnett Oil Co., Inc.Feb 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
9916-99DrillPetro Oil & Gas, Inc.Oct 17, 1977Oct 17, 1977—1,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-3335————
—— O-1-5737————

Perforations

Perforated and open-hole intervals.

FromToType
896902Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2890——
4.59456.75145 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
00Feb 6, 1997Jul 28, 1978—
00Jan 12, 1984Jul 28, 1978—

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