TEXAS · WELLS · GONZALES COUNTY · KING FEHNER UNIT LEASE · API 42-177-32794 · DISTRICT 01

King Fehner Unit #8H

Y

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

King Fehner Unit #8H (API 42-177-32794) is a horizontal well in Gonzales County operated by Eog Resources Inc., completed March 7, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 7, 2012, permitted to 11,453 ft.

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

Its lease has reported 2.26M barrels of oil and 4.42M mcf of gas since May 2011, last reporting in July 2026. The lease carries 14 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
16,348
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Apr 2026
Latest permitEOG Resources, Inc.Dec 7, 2012
11,453
total depth, ft
1
permits on file
Dec 7, 2012
last permit issued
Mar 7, 2013
completed
2.26M
cumulative oil, bbl
4.42M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 7, 2013
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.

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
King Fehner Unit O-1-15509Eagleville (Eagle Ford-1)EOG Resources, Inc.142.26M4.42MMay 2011 – Jul 2026

Oil, barrels lease total

Last 12 months 31,082 · prior 12 36,299(-14%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 67,871 · prior 12 100,782(-33%)

05K10K15K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Jun 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
752070-99DrillEOG Resources, Inc.Nov 26, 2012Dec 7, 2012Jan 19, 201312,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 7, 2013King Fehner Unit O-1-15509Eagleville (Eagle Ford-1)EOG Resources Inc.Producing11,453

Formation tops

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

FormationMD ftSubsea
Anacacho10,150-9,847
Austin Chalk10,544-10,241
Eagle Ford10,970-10,667

Perforations

Perforated and open-hole intervals.

FromToType
11,44415,934Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,51012.25807 S
5.516,5138.52,555 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
00Jun 28, 2013Apr 30, 2013Yes

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