WELL · 42-317-33127 · DISTRICT 8

Millhollon Trust #1

Plugged

Martin County · Spraberry (Trend Area) field  · Vertical

Millhollon Trust #1 (API 42-317-33127) is a plugged well in Martin County, plugged May 22, 2013, last operated by Reatta Energy Inc..

The RRC has issued one drilling permit, issued January 24, 1985, permitted to 8,800 ft.

It was permitted by Wilton Oil Company and has since transferred to Reatta Energy Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including T/Upper Spraberry, T/Lower Spraberry, T/Dean.

Its lease has reported 23.5K barrels of oil and 149K mcf of gas since January 1993, last reporting in September 2014.

Operator of record

Reatta Energy Inc.

Permitted by Wilton Oil Company; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jun 4, 2026 · 61 permits on file · (432) 853-9557

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleReatta Energy Inc.
Production reportsReatta Energy, Inc.through Aug 2012
Latest permitWilton Oil CompanyJan 24, 1985

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

8,800
total depth, ft
1
permits on file
Jan 24, 1985
last permit issued
Apr 13, 1985
completed
23.5K
cumulative oil, bbl
149K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 13, 1985
Shut in
—
Plugged
May 22, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Millhollon Trust O-10-30006Spraberry (Trend Area)Reatta Energy, Inc.123.5K149KJan 1993 – Sep 2014

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. 1Wilton Oil CompanyJan 1993 → Aug 1998
  2. 2Reatta Energy, Inc.Sep 1998 → Aug 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
265176-99DrillWilton Oil CompanyJan 23, 1985Jan 24, 1985Feb 7, 19858,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-30006————

Formation tops

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

FormationMD ftSubsea
T/Upper Spraberry6,932-4,235
T/Lower Spraberry7,736-5,039
T/Dean8,168-5,471

Perforations

Perforated and open-hole intervals.

FromToType
7,0827,550Perforated
7,6477,926Perforated
8,1778,463Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37527117.5300 S
8.6253,53011200 S
4.58,6487.8751,200 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 26, 1985Jul 31, 1985—
00Aug 14, 1985——

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