WELL · 42-401-32200 · DISTRICT 6

Holmes #1

Y

Rusk County · Walkers Chapel (Travis Peak) field · Temp Abandoned  · Vertical

Holmes #1 (API 42-401-32200) is a well in Rusk County operated by Ponta E&P LLP, completed August 1, 1988 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 28, 1988, permitted to 9,000 ft.

It was permitted by Odegard Energy, Inc. and has since transferred to Ponta E&P LLP on the wellbore schedule.

Completion filings report 4 formation tops, including B/Austin Chalk, B/Massive Anhydrite, T/Pettit, T/Travis Peak.

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

Operator of record

Ponta E&P LLP

Permitted by Odegard Energy, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Mar 4, 2026 · 2 permits on file · (903) 353-0372

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePonta E&P LLP
Production reportsPatara Oil & Gas LLCthrough May 2010
Latest permitOdegard Energy, Inc.Mar 28, 1988

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

9,000
total depth, ft
1
permits on file
Mar 28, 1988
last permit issued
Aug 1, 1988
completed
0
cumulative oil, bbl
117K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 1, 1988
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Holmes G-6-128583Walkers Chapel (Travis Peak)Ponta E&P LLP10117KJan 1993 – 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. 1Odegard Energy, Inc.Jan 1993 → May 2005
  2. 2AC Exploration, LLCJun 2005 → Aug 2008
  3. 3Patara Oil & Gas LLCSep 2008 → May 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
344252-99DrillOdegard Energy, Inc.Mar 23, 1988Mar 28, 1988—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-128583————

Formation tops

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

FormationMD ftSubsea
B/Austin Chalk3,318-3,043
B/Massive Anhydrite7,277-7,002
T/Pettit7,990-7,715
T/Travis Peak8,350-8,075

Perforations

Perforated and open-hole intervals.

FromToType
8,4208,428Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,57811425 S
4.58,5777.875675 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
00Nov 15, 1988Oct 31, 1988—
00Oct 25, 1988Sep 26, 1988Yes
00Oct 18, 1988——

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