TEXAS · WELLS · PALO PINTO COUNTY · STUART ESTATE "59" LEASE · API 42-363-34241 · DISTRICT 6E

Stuart Estate 59 #1

Plugged

Palo Pinto County · Cumming (Conglomerate) field  · Vertical

Stuart Estate 59 #1 (API 42-363-34241) is a plugged well in Palo Pinto County, plugged April 20, 1996, last operated by Cumming Company Inc. The.

The RRC has issued one drilling permit, issued January 27, 1994, permitted to 4,100 ft.

Completion filings report 5 formation tops, including Strawn, Caddo, Lake Sand, Conglomerate.

Its lease has reported 53.4K mcf of gas since February 1994, with no volume in the three years through April 2026.

Operator of record

Cumming Company Inc. The

Based in
Fort Worth, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 18, 2026
Permits on file
410
Phone
(817) 737-2393

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCumming Company Inc. The
Production reportsCumming Company, Inc. Thethrough Apr 1995
Latest permitCumming Company, Inc. TheJan 27, 1994
4,100
total depth, ft
1
permits on file
Jan 27, 1994
last permit issued
Feb 17, 1994
completed
0
cumulative oil, bbl
53.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1994 THROUGH Apr 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 17, 1994
Shut in
—
Plugged
Apr 20, 1996

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
Stuart Estate "59" G-8-148509Cumming (Conglomerate)Cumming Company, Inc. The1053.4KFeb 1994 – Apr 1995

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. 1Cumming Company, Inc. TheFeb 1994 → Apr 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
420566-99DrillCumming Company, Inc. TheJan 26, 1994Jan 27, 1994Feb 2, 19944,100

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 17, 1994Stuart Estate 59 G-8-148509Cumming (Conglomerate)Cumming Company Inc. ThePlugged—

Formation tops

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

FormationMD ftSubsea
StrawnUPPER STRAWN1,170162
StrawnLOWER STRAWN1,722-390
Caddo3,170-1,838
Lake Sand3,240-1,908
Conglomerate3,795-2,463
Marble Falls3,980-2,648

Perforations

Perforated and open-hole intervals.

FromToType
3,7953,803Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62525012.25150 S
4.53,9857.875150 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Mar 31, 1994Mar 24, 1994Yes
00Mar 29, 1994——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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