WELL · 42-213-30569 · DISTRICT 5

Ogu (Huff, C.C. #3) #118

N

Henderson County  · Vertical

Ogu (Huff, C.C. #3) #118 (API 42-213-30569) is a permitted well in Henderson County filed by Xto Energy Inc.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 1986 and 2010, permitted to 12,200 ft.

Completion filings report 4 formation tops, including Rodessa, Pettit, Travis Peak, Cotton Valley.

Operator of record

XTO Energy Inc.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,153 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsUrban Oil & Gas Group, LLCthrough Apr 2026
Latest permitXTO Energy Inc.Apr 2, 2010
12,200
total depth, ft
3
permits on file
Apr 2, 2010
last permit issued
—
completed
0
cumulative oil, bbl
1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ogu (Huff, C. C. -3) G-5-123158Opelika (Travis Peak)Urban Oil & Gas Group, LLC101MJan 1993 – Jul 2026
Ogu (Huff C. C. 3) G-5-186221Opelika (Rodessa)Urban Oil & Gas Group, LLC100Nov 2001 – Jul 2026

Gas, mcf lease total

Last 12 months 10,826 · prior 12 7,317(+48%)

05001K1.5K202420252026

Chain of custody

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

  1. 1EP Operating Limited PartnershipJan 1993 → Feb 1995
  2. 2Enserch Exploration, IncMar 1995 → Mar 1998
  3. 3Eex CorporationApr 1998 → Apr 1998
  4. 4Cross Timbers Operating CompanyMay 1998 → May 2001
  5. 5XTO Energy Inc.Jun 2001 → Jan 2025
  6. 6Urban Oil & Gas Group, LLCFeb 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
693599-99RecompletionXTO Energy Inc.Mar 29, 2010Apr 2, 2010—12,048
515873-99RecompletionXTO Energy Inc.Dec 6, 2001Dec 11, 2001Nov 27, 200112,048
304933-99DrillEP Operating CompanyAug 4, 1986Aug 6, 1986—12,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-123158————
—— G-5-186221————

Formation tops

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

FormationMD ftSubsea
Rodessa7,854-7,470
Pettit8,587-8,203
Travis Peak8,718-8,334
Cotton Valley10,425-10,041

Perforations

Perforated and open-hole intervals.

FromToType
7,8608,048Perforated
9,0289,816Perforated
9,04010,330Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,20511340 S
5.512,0507.8751,300 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 25, 2002Dec 14, 2001—
00Jan 7, 2002——
00Feb 13, 1987Jan 22, 1987Yes
00Feb 6, 1987——

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