WELL · 42-089-32584 · DISTRICT 3

Thomas Trust #1

Y

Colorado County · Lissie W. (Wilcox Upper) field · Temp Abandoned  · Vertical

Thomas Trust #1 (API 42-089-32584) is a well in Colorado County operated by Wagner Oil Company, completed November 2, 2008 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued August 26, 2008, permitted to 10,000 ft.

It was permitted by Ascent Operating, LP and has since transferred to Wagner Oil Company on the wellbore schedule.

Completion filings report 5 formation tops, including Frio, Vicksburg, Yegua, Cook Mountain.

No lease production has been reported under this well’s leases.

Operator of record

Wagner Oil Company

Permitted by Ascent Operating, LP; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 278 permits on file · (800) 457-5332

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWagner Oil Company
Production reportsHalcon Resources Operating, Inc.through Sep 2013
Latest permitAscent Operating, LPAug 26, 2008

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

10,000
total depth, ft
1
permits on file
Aug 26, 2008
last permit issued
Nov 2, 2008
completed
0
cumulative oil, bbl
35.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 2, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Thomas Trust G-3-244799Lissie, W. (Wilcox Upper)Wagner Oil Company1035.2KNov 2008 – 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. 1Ram Operating Company, Inc.Mar 2009 → Mar 2012
  2. 2Halcon Resources Operating, Inc.Jan 2013 → Sep 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
668489-99DrillAscent Operating, LPAug 6, 2008Aug 26, 2008Sep 22, 200810,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-244799————

Formation tops

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

FormationMD ftSubsea
Frio2,900-2,736
Vicksburg4,640-4,476
Yegua6,100-5,936
Cook Mountain7,600-7,436
Wilcox9,630-9,466

Perforations

Perforated and open-hole intervals.

FromToType
9,7869,798Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1660——
8.6253,07012.251,375 S
4.59,9557.875165 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
00Mar 3, 2009Nov 26, 2008Yes
00Feb 10, 2009——

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