WELL · 42-602-30124 · DISTRICT 4

State Tract 926-S #1

Plugged

Mustang IS-SB County · Block 926-S (Frio 9200) field  · Vertical

State Tract 926-S #1 (API 42-602-30124) is a plugged well in Mustang IS-SB County, plugged September 4, 2005, last operated by Dunhill Resources Inc..

The RRC has issued 3 drilling permits between 1981 and 1993, permitted to 10,800 ft.

It was permitted by Mitchell Energy Corporation and has since transferred to Dunhill Resources Inc. on the wellbore schedule.

Operator of record

Dunhill Resources Inc.

Permitted by Mitchell Energy Corporation; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed May 6, 2005

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDunhill Resources Inc.
Production reportsMitchell Energy Corporationthrough Feb 1997
Latest permitMitchell Energy CorporationFeb 4, 1993

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

10,800
total depth, ft
3
permits on file
Feb 4, 1993
last permit issued
Mar 4, 1993
completed
0
cumulative oil, bbl
602K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2005

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 4, 1993
Shut in
—
Plugged
Sep 4, 2005

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 3 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Tract 926-S G-4-133992Block 926-S (Frio 9400)Dunhill Resources, Inc.100Jan 1993 – Sep 2005
State Tract 926-S G-4-146340Block 926-S (Frio 9200)Dunhill Resources, Inc.10602KMar 1993 – Sep 2005
— G-4-101246——000—

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. 1Mitchell Energy CorporationMar 1993 → Feb 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
408779-99RecompletionMitchell Energy CorporationFeb 4, 1993Feb 4, 1993Feb 12, 19939,788
357745-99RecompletionMitchell Energy CorporationApr 4, 1989Apr 5, 1989—10,224
107338-99DrillMitchell Energy Offshore Corp.Feb 3, 1981Feb 3, 1981Jun 9, 198110,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-101246————
—— G-4-133992————
—— G-4-146340————

Perforations

Perforated and open-hole intervals.

FromToType
9,2709,278Perforated
9,4089,415Perforated
10,04210,066Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
16801221,330 S
10.752,94414.752,000 S
7.6257,5959.875575 S
2.8759,216——

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
00Nov 15, 1993Apr 22, 1993Yes
00Sep 8, 1993—Yes
00Apr 26, 1990Dec 11, 1989Yes
00Apr 19, 1990——
00Jan 12, 1984Aug 6, 1982—

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