TEXAS · WELLS · SAN AUGUSTINE COUNTY · MITCHELL, RUDY LEASE · API 42-405-30266 · DISTRICT 06

Mitchell Rudy #1H

Y

San Augustine County · Carthage (Haynesville Shale) field · Producing  · Horizontal

Mitchell Rudy #1H (API 42-405-30266) is a horizontal well in San Augustine County operated by Xto Energy Inc., completed November 7, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued March 25, 2009, permitted to 12,754 ft.

Completion filings report 6 formation tops, including Pettit, Travis Peak, Knowles, Bossier.

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

Operator of record

XTO Energy Inc.

Based in
Spring, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
16,156
Phone
(346) 502-1572

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitXTO Energy Inc.Mar 25, 2009
12,754
total depth, ft
3
permits on file
Mar 25, 2009
last permit issued
Nov 7, 2009
completed
0
cumulative oil, bbl
1.69M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 7, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Mitchell, Rudy G-6-255050Carthage, North (Bossier Shale)XTO Energy Inc.101.69MNov 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 11,504 · prior 12 14,275(-19%)

01K2K202420252026

Chain of custody

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

  1. 1XTO Energy Inc.Nov 2009 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
679562-97DrillXTO Energy Inc.Dec 17, 2009Mar 25, 2009May 11, 200914,500
679562-98DrillXTO Energy Inc.Jul 8, 2009Mar 25, 2009May 11, 200914,500
679562-99DrillXTO Energy Inc.Mar 17, 2009Mar 25, 2009May 11, 200914,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 7, 2009Mitchell Rudy G-6-255050Carthage (Haynesville Shale)XTO Energy Inc.Producing12,754

Formation tops

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

FormationMD ftSubsea
Pettit7,541-7,299
Travis Peak8,222-7,980
Knowles10,698-10,456
Bossier12,195-11,953
Haynesville12,654-12,412
Cotton ValleyCOTTON VALLEY LIME12,826-12,584

Perforations

Perforated and open-hole intervals.

FromToType
13,05015,563Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,21312.25850 S
712,0008.751,415 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
00May 20, 2010Dec 21, 2009Yes
00Mar 17, 2010——

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