TEXAS · WELLS · CRANE COUNTY · CORDONA LAKE CONSOLIDATED UNIT LEASE · API 42-103-33657 · DISTRICT 7B

Cordona Lake Consolidated Unit #80H

On schedule

Crane County · Cordona Lake field · Producing  · Horizontal

Cordona Lake Consolidated Unit #80H (API 42-103-33657) is a horizontal well in Crane County operated by Hilcorp Energy Company, completed June 16, 2008 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 1985 and 2008, permitted to 5,702 ft.

It was permitted by Xto Energy Inc. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 8 formation tops, including Rustler, Yates, San Andres, San Angelo.

Its lease has reported 11.7M barrels of oil and 40M mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 176 wells, so these are lease totals, not this well alone.

Operator of record

Hilcorp Energy Company

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

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 27, 2026
Permits on file
3,458
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitXTO Energy Inc.May 1, 2008

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

5,702
total depth, ft
2
permits on file
May 1, 2008
last permit issued
Jun 16, 2008
completed
11.7M
cumulative oil, bbl
40M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 16, 2008
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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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; they carry 176 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cordona Lake Consolidated Unit O-10-20582Cordona LakeHilcorp Energy Company17611.7M40MJan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 152,351 · prior 12 112,971(+35%)

010K20K202420252026

Gas, mcf lease total

Last 12 months 677,200 · prior 12 653,948(+4%)

050K100K202420252026

Wells named Cordona Lake Consolidated Unit

Hilcorp Energy Company's other wells filed under this lease name in Crane County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Exxon Corp.Jan 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Jun 2005
  3. 3XTO Energy Inc.Jul 2005 → Feb 2025
  4. 4Hilcorp Energy CompanyApr 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
660029-99RecompletionXTO Energy Inc.Apr 18, 2008May 1, 2008Mar 12, 20086,800
273081-99DrillExxon Corp.Apr 8, 1985Apr 22, 1985Jun 2, 19855,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 16, 2008Cordona Lake Consolidated Unit O-10-20582Cordona LakeHilcorp Energy CompanyProducing5,702
Jun 16, 2008Cordona Lake Consolidated Unit O-10-20582Cordona LakeHilcorp Energy CompanyProducing5,702
Nov 11, 1995Cordona Lake Consolidated Unit O-10-20582Cordona LakeHilcorp Energy CompanyNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Rustler4621,890
Yates1,505847
San Andres2,878-526
San Angelo3,335-983
San Angelo3,408-1,056
Clear ForkUPPER CLEARFORK3,801-1,449
Clear ForkUPPER CLEARFORK3,802-1,450
Tubb4,057-1,705
Clear ForkLOWER CLEARFORK4,150-1,798
Clear ForkLOWER CLEARFORK4,195-1,843
Wichita-AlbanyWICHITA ALBANY4,564-2,212
Wichita-AlbanyWICHITA4,567-2,215
Devonian5,465-3,113

Perforations

Perforated and open-hole intervals.

FromToType
5,3096,724Open hole
5,4545,530Perforated
5,4545,550Perforated
5,4545,554Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62563112.25400 S
8.62563512.25400 S
5.55,7007.8751,930 S
5.55,7027.8751,930 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 17, 2009Dec 5, 2008Yes
00Jul 16, 2009Dec 4, 1995—
00Jun 25, 1996Dec 4, 1995—
00Oct 9, 1985Sep 30, 1985—
00Oct 5, 1985——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.

Find logs withinmiles of this well:List →Map →

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