WELL · 42-289-31630 · DISTRICT 5

Dot Cadenhead -D- #1

Y

Leon County · Red Oak (Dexter) field · Water Supply  · Vertical

Dot Cadenhead -D- #1 (API 42-289-31630) is a well in Leon County operated by Rusk Energy Operating LLC, completed July 1, 2011 and listed as water supply on the RRC schedule.

The RRC has issued one drilling permit, issued December 15, 2006, permitted to 7,000 ft.

It was permitted by Diasu Oil & Gas CO., Inc. and has since transferred to Rusk Energy Operating LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Nacatoch, Pecan Gap, Austin Chalk, Woodbine.

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

Operator of record

Rusk Energy Operating LLC

Permitted by Diasu Oil & Gas Co., Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Nov 4, 2025 · 16 permits on file · (713) 252-6566

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRusk Energy Operating LLC
Production reportsXTO Energy Inc.through Aug 2009
Latest permitDiasu Oil & Gas Co., Inc.Dec 15, 2006

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

7,000
total depth, ft
1
permits on file
Dec 15, 2006
last permit issued
Jul 1, 2011
completed
0
cumulative oil, bbl
709K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 1, 2011
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
Dot Cadenhead -D- G-5-228170Red Oak (Dexter)Rusk Energy Operating LLC10709KMar 2007 – 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. 1XTO Energy Inc.Mar 2007 → Aug 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
630531-99DrillDiasu Oil & Gas Co., Inc.Dec 14, 2006Dec 15, 2006Jan 13, 20077,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-228170————

Formation tops

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

FormationMD ftSubsea
Nacatoch3,320-3,020
Pecan Gap4,120-3,820
Austin ChalkAUSTIN5,253-4,953
Austin ChalkBASE AUSTIN5,579-5,279
Woodbine6,056-5,756

Perforations

Perforated and open-hole intervals.

FromToType
6,4676,474Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62573111216 S
8.62575011216 S
5.56,7507.875823 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
00Feb 21, 2012Oct 7, 2011Yes
00Aug 30, 2007May 11, 2007Yes
00Jul 18, 2007——

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