WELL · 42-481-32973 · DISTRICT 3

Mick A. D. #5

Plugged

Wharton County · Boling (Iago) field  · Vertical

Mick A. D. #5 (API 42-481-32973) is a plugged well in Wharton County, plugged January 31, 2024, last operated by Duderstadt A. R..

The RRC has issued one drilling permit, issued June 4, 1986, permitted to 4,900 ft.

It was permitted by Hagen-Greenbriar Expl. Corp. and has since transferred to Duderstadt A. R. on the wellbore schedule.

Completion filings report 5 formation tops, including B/Fresh H2o Sands, B/Mass Miocene Sand, Het Lime, 1st Mass. Frio Sand.

Its lease has reported 123 barrels of oil and 13 mcf of gas since January 1993, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Duderstadt A. R.

Permitted by Hagen-Greenbriar Expl. Corp.; the EWA schedule now lists a different operator.

Boling, TX · P-5 Y, filed Jan 5, 2024 · (979) 657-4685

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDuderstadt A. R.
Production reportsDuderstadt, A. R.through Jul 1995
Latest permitHagen-Greenbriar Expl. Corp.Jun 4, 1986

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

4,900
total depth, ft
1
permits on file
Jun 4, 1986
last permit issued
Aug 1, 1986
completed
123
cumulative oil, bbl
13
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 1, 1986
Shut in
—
Plugged
Jan 31, 2024

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mick, A. D. O-3-7387Boling (Iago)Duderstadt, A. R.512313Jan 1993 – Jul 2026

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. 1Duderstadt, A. R.Oct 1993 → Jul 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
302855-99DrillHagen-Greenbriar Expl. Corp.Jul 11, 1986Jun 4, 1986Jul 8, 19864,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-7387————

Formation tops

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

FormationMD ftSubsea
B/Fresh H2O Sands1,208-1,128
B/Mass Miocene Sand4,242-4,162
Het Lime4,432-4,352
1ST Mass. Frio Sand4,617-4,537
JacksonJACKSON FM4,658-4,578

Perforations

Perforated and open-hole intervals.

FromToType
4,6194,623Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62543812.25240 S
5.54,7848.751,410 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
00Sep 9, 1986Aug 13, 1986Yes
00Sep 6, 1986——

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