TEXAS · WELLS · HEMPHILL COUNTY · JONES TRUST -26- LEASE · API 42-211-32634 · DISTRICT 08

Jones Trust -26- #4A

Plugged

Hemphill County · Canadian SE (Douglas) field  · Vertical

Jones Trust -26- #4A (API 42-211-32634) is a plugged well in Hemphill County, plugged March 19, 2009, last operated by Chesapeake Operating Inc..

The RRC has issued one drilling permit, issued August 14, 2002, permitted to 9,500 ft.

It was permitted by El Paso Production Company and has since transferred to Chesapeake Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Douglas, Tonkawa.

Operator of record

Chesapeake Operating Inc.

Permitted by El Paso Production Company; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2024
Permits on file
13,061
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reportsChesapeake Operating, Inc.through Mar 2009
Latest permitEl Paso Production CompanyAug 14, 2002

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

9,500
total depth, ft
1
permits on file
Aug 14, 2002
last permit issued
Sep 9, 2002
completed
0
cumulative oil, bbl
39.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2002 THROUGH May 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 9, 2002
Shut in
—
Plugged
Mar 19, 2009

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 Trust -26- G-14-190962Canadian, SE (Douglas)Chesapeake Operating, Inc.1039.7KSep 2002 – May 2009

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. 1El Paso Production CompanySep 2002 → Apr 2003
  2. 2Chesapeake Operating, Inc.May 2003 → Mar 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
522772-99DrillEl Paso Production CompanyAug 14, 2002Aug 14, 2002Aug 22, 20029,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 9, 2002Jones Trust -26- G-14-190962Canadian SE (Douglas)Chesapeake Operating Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Douglas7,120-4,620
Tonkawa7,710-5,210

Perforations

Perforated and open-hole intervals.

FromToType
7,7647,819Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,24012.25700 S
4.57,9537.875475 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 29, 2002Oct 4, 2002Yes
00Oct 15, 2002——

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