WELL · 42-001-32409 · DISTRICT 6

James Trust #1

Y

Anderson County · Concord Dome (Rodessa) field · Temp Abandoned  · Vertical

James Trust #1 (API 42-001-32409) is a well in Anderson County operated by Armor Resources LLC, completed May 10, 2003 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued February 11, 2003, permitted to 12,900 ft.

It was permitted by J-W Operating CO. and has since transferred to Armor Resources LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Top Salt, Bottom Salt, Rodessa.

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

Operator of record

Armor Resources LLC

Permitted by J-W Operating Co.; the EWA schedule now lists a different operator.

Longview, TX · P-5 Y, filed Jan 4, 2026 · (903) 704-0989

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleArmor Resources LLC
Production reportsArmor Resources LLCthrough Jul 2016
Latest permitJ-W Operating Co.Feb 11, 2003

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

12,900
total depth, ft
1
permits on file
Feb 11, 2003
last permit issued
May 10, 2003
completed
0
cumulative oil, bbl
197K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 10, 2003
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
James Trust G-6-195764Concord Dome (Rodessa)Armor Resources LLC10197KMay 2003 – 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. 1J-W Operating Co.May 2003 → Jun 2007
  2. 2Fortune Resources LLCJul 2007 → Mar 2016
  3. 3Armor Resources LLCMay 2016 → Jul 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
528358-99DrillJ-W Operating Co.Feb 11, 2003Feb 11, 2003Feb 27, 200312,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-195764————

Formation tops

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

FormationMD ftSubsea
Top Salt5,960-5,296
Bottom Salt8,330-7,666
RodessaTOP RODESSA10,100-9,436

Perforations

Perforated and open-hole intervals.

FromToType
10,52610,536Perforated
10,62810,658Perforated
10,76810,774Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37586117.5694 S
9.6256,03412.25385 S
5.512,2988.751,375 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 8, 2003Jul 7, 2003Yes
00Aug 1, 2003——

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