TEXAS · WELLS · GONZALES COUNTY · CORNFIELD UNIT LEASE · API 42-177-32499 · DISTRICT 01

Cornfield Unit #1H

On schedule

Gonzales County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Cornfield Unit #1H (API 42-177-32499) is a horizontal well in Gonzales County operated by Eog Resources Inc., completed May 7, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 9, 2012, permitted to 11,800 ft.

Completion filings report 3 formation tops, including Anancacho, Austin Chalk, Eagle Ford.

Its lease has reported 559K barrels of oil and 1.45M mcf of gas since May 2012, last reporting volume in August 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Aug 12, 2026
Permits on file
16,354
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Aug 2026
Latest permitEOG Resources, Inc.Mar 9, 2012
11,800
total depth, ft
1
permits on file
Mar 9, 2012
last permit issued
May 7, 2012
completed
559K
cumulative oil, bbl
1.45M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · MAY 2012 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 7, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cornfield Unit O-1-15934Eagleville (Eagle Ford-1)EOG Resources, Inc.16559K1.45MMay 2012 – Aug 2026

Oil, barrels lease total

Last 12 months 9,877 · prior 12 12,458(-21%)

01K2K202420252026

Gas, mcf lease total

Last 12 months 44,431 · prior 12 46,768(-5%)

05K10K202420252026

Wells named Cornfield Unit

EOG Resources Inc.'s other wells filed under this lease name in Gonzales 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

Operator on the lease's P-4

Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.

OperatorFromTo
EOG Resources, Inc.May 7, 2012today

Reporting production

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

  1. 1EOG Resources, Inc.May 2012 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
735355-99DrillEOG Resources, Inc.Mar 6, 2012Mar 9, 2012Mar 28, 201212,800

Completions

CompletedLeaseFieldOperatorStatusDepth
May 7, 2012Cornfield Unit O-1-15934Eagleville (Eagle Ford-1)EOG Resources Inc.Producing11,800

Formation tops

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

FormationMD ftSubsea
Anancacho10,507-10,183
Austin Chalk10,901-10,577
Eagle FordEAGLEFORD11,284-10,960

Perforations

Perforated and open-hole intervals.

FromToType
11,71816,015Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6255,00512.251,604 S
5.516,1038.52,415 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 14, 2012Jun 19, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Apr 23, 2015. Resistivity.

Click a log to get its files from the RRC (free account). It opens in a new tab on the RRC's log search for this well, which lists each file to view or download; the RRC has no address for a single file.

Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Anancacho, Austin Chalk, Eagle FordTIFF7,000 to 16,103Apr 23, 2015run Apr 10, 20120.96

"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.

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.

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