WELL · 42-365-35298 · DISTRICT 6

Jones Elsie #10

Y

Panola County · Carthage (Cotton Valley) field · Producing  · Vertical

Jones Elsie #10 (API 42-365-35298) is a well in Panola County operated by Xto Energy Inc., completed July 7, 2004 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 23, 2004, permitted to 9,600 ft.

It was permitted by Classic Energy Incorporated and has since transferred to Xto Energy Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including James Lime, Pettit, Travis Peak, Cotton Valley.

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

Operator of record

XTO Energy Inc.

Permitted by Classic Energy Incorporated; the EWA schedule now lists a different operator.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,156 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitClassic Energy IncorporatedMar 23, 2004

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

9,600
total depth, ft
1
permits on file
Mar 23, 2004
last permit issued
Jul 7, 2004
completed
0
cumulative oil, bbl
931K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 7, 2004
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Jones, Elsie G-6-203280Carthage (Cotton Valley)XTO Energy Inc.10931KJul 2004 – Jul 2026

Gas, mcf lease total

Last 12 months 5,040 · prior 12 7,926(-36%)

01K2K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Exxon Mobil CorporationJul 2004 → Dec 2013
  2. 2XTO Energy Inc.Jan 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
543531-99DrillClassic Energy IncorporatedMar 22, 2004Mar 23, 2004May 13, 20049,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-203280————

Formation tops

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

FormationMD ftSubsea
James Lime5,448-5,209
PettitUPPER PETTIT5,714-5,475
Travis Peak6,202-5,963
Cotton Valley8,286-8,047

Perforations

Perforated and open-hole intervals.

FromToType
8,7669,224Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
11.751,07614.75480 S
8.6255,29610.625500 S
4.59,3507.8751,290 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
00Oct 18, 2004Aug 2, 2004Yes
00Sep 14, 2004——

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