TEXAS · WELLS · YOAKUM COUNTY · CORNELL UNIT LEASE · API 42-501-36165 · DISTRICT 7B

Cornell Unit #3076

On schedule

Yoakum County · Wasson field · Producing  · Directional

Cornell Unit #3076 (API 42-501-36165) is a well in Yoakum County operated by Hilcorp Energy Company, completed August 15, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 25, 2013, permitted to 5,499 ft.

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

Completion filings report 3 formation tops, including Queen, Grayburg, San Andres.

Its lease has reported 20.4M barrels of oil and 35.7M mcf of gas since the record begins in January 1993, last reporting volume in August 2026. The lease carries 268 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 (A)
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.Apr 25, 2013

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

5,499
total depth, ft
1
permits on file
Apr 25, 2013
last permit issued
Aug 15, 2013
completed
20.4M
cumulative oil, bbl
35.7M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 15, 2013
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 AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 268 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cornell Unit O-11-19453WassonHilcorp Energy Company26820.4M35.7Mby Jan 1993 – Aug 2026

Oil, barrels lease total

Last 12 months 481,396 · prior 12 448,831(+7%)

020K40K60K202420252026

Gas, mcf lease total

Last 12 months 702,433 · prior 12 651,221(+8%)

050K100K202420252026

Wells named Cornell Unit

Hilcorp Energy Company's other wells filed under this lease name in Yoakum 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 → Jul 2000
  3. 3Cross Timbers Operating CompanyAug 2000 → May 2001
  4. 4XTO Energy Inc.Jun 2001 → Mar 2025
  5. 5Hilcorp Energy CompanyApr 2025 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
759511-99DrillXTO Energy Inc.Mar 26, 2013Apr 25, 2013May 15, 20135,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 15, 2013Cornell Unit O-11-19453WassonHilcorp Energy CompanyProducing5,499

Formation tops

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

FormationMD ftSubsea
Queen3,725-132
Grayburg4,405-812
San Andres4,676-1,083

Perforations

Perforated and open-hole intervals.

FromToType
4,9485,293Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,253111,020 S
5.55,5487.8751,150 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
00May 30, 2014Sep 4, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Oct 30, 2014. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Queen, Grayburg, San AndresTIFF0 to 5,496Oct 30, 2014run Jun 3, 20136.47

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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