WELL · 42-235-32081 · DISTRICT 7

UT-39A #2

Plugged

Irion County · Probandt (Canyon) field  · Vertical

UT-39a #2 (API 42-235-32081) is a plugged well in Irion County, plugged July 25, 2013, last operated by Meadco Properties.

The RRC has issued one drilling permit, issued April 19, 1983, permitted to 7,500 ft.

Completion filings report 11 formation tops, including Seven Rivers, Queen, Grayburg, San Andres.

Its 2 leases have reported 885 barrels of oil and 32.9K mcf of gas since January 1993, last reporting in April 2014. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Meadco Properties

Midland, TX · P-5 Y, filed May 4, 2026 · 126 permits on file · (432) 557-6695

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMeadco Properties
Production reportsMeadco Propertiesthrough Dec 2011
Latest permitMeadco PropertiesApr 19, 1983
7,500
total depth, ft
1
permits on file
Apr 19, 1983
last permit issued
Dec 20, 1984
completed
885
cumulative oil, bbl
32.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 20, 1984
Shut in
—
Plugged
Jul 25, 2013

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
U.T. 39 "A" G-9-189606Probandt (Canyon)Meadco Properties106.83KJun 2002 – Apr 2014
UT-39A O-9-11614Probandt (Canyon)Meadco Properties288526KJan 1993 – Feb 2005

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. 1Meadco PropertiesJan 1993 → Dec 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
191795-99DrillMeadco PropertiesApr 19, 1983Apr 19, 1983—7,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-189606————
—— O-9-11614————

Formation tops

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

FormationMD ftSubsea
Seven Rivers7851,659
Queen1,0201,424
Grayburg1,2361,208
San Andres1,581863
San Andgelo2,110334
San Angelo2,110334
Spraberry4,300-1,856
SpraberrySPRAYBERRY4,300-1,856
Dean5,443-2,999
Wolfcamp5,665-3,221
Permian (undifferentiated)BASE PERMIAN6,689-4,245
Canyon6,850-4,406

Perforations

Perforated and open-hole intervals.

FromToType
6,8506,955Perforated
6,9857,015Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62585811325 S
2.3756,892——
4.57,1547.875750 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
00Aug 23, 2002Jul 10, 2002—
00Jul 31, 2002——
00Nov 7, 1985Jan 16, 1985—
00Nov 1, 1985——
00Jan 30, 1985Jan 16, 1985—
00Jan 12, 1984May 27, 1983—

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) and the University Lands library. 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/23532081, documented in the API reference.