WELL · 42-363-34676 · DISTRICT 7

Houx J. #1

Plugged

Palo Pinto County · Bob Richards Ranch (Congl.) field  · Vertical

Houx J. #1 (API 42-363-34676) is a plugged well in Palo Pinto County, plugged March 26, 2026, last operated by Eagleridge Operating LLC.

The RRC has issued one drilling permit, issued July 2, 1997, permitted to 5,000 ft.

It was permitted by United Energy Partners, Inc. and has since transferred to Eagleridge Operating LLC on the wellbore schedule.

Completion filings report 5 formation tops, including "A" Congl., "B" Congl., "D" Congl., Marble Falls.

Operator of record

Eagleridge Operating LLC

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

Dallas, TX · P-5 Y, filed Jan 4, 2026 · 129 permits on file · (855) 820-6008

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEagleridge Operating LLC
Production reportsVantage Fort Worth Energy LLCthrough Jul 2010
Latest permitUnited Energy Partners, Inc.Jul 2, 1997

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

5,000
total depth, ft
1
permits on file
Jul 2, 1997
last permit issued
Oct 24, 1997
completed
0
cumulative oil, bbl
95.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1997 THROUGH Mar 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 24, 1997
Shut in
—
Plugged
Mar 26, 2026

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
Houx, J. G-8-165382Bob Richards Ranch (Congl.)Eagleridge Operating, LLC1095.5KOct 1997 – Mar 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. 1United Energy Partners, Inc.Oct 1997 → Oct 2000
  2. 2Telesis Operating Co., Inc.Nov 2000 → Jul 2008
  3. 3Vantage Fort Worth Energy LLCAug 2008 → Jul 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
464512-99DrillUnited Energy Partners, Inc.Jul 2, 1997Jul 2, 1997Sep 21, 19975,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-165382————

Formation tops

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

FormationMD ftSubsea
"A" Congl.3,211-2,295
"B" Congl.3,289-2,373
"D" Congl.3,459-2,543
Marble Falls3,625-2,709
Ellen.4,016-3,100

Perforations

Perforated and open-hole intervals.

FromToType
3,2223,226Perforated
3,2313,234Perforated
3,2403,250Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62524912.25150 S
4.54,0867.875300 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
00Jan 20, 1998Nov 17, 1997Yes
00Dec 5, 1997——

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