TEXAS · WELLS · WILSON COUNTY · DALY UNIT LEASE · API 42-493-32792 · DISTRICT 01
Daly Unit #2H
Wilson County · Eagleville (Eagle Ford-1) field · Producing · Horizontal
Daly Unit #2H (API 42-493-32792) is a horizontal well in Wilson County operated by Eog Resources Inc., completed July 10, 2014 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued May 23, 2014, permitted to 9,876 ft.
Completion filings report 9 formation tops, including Yegua, Queen City, Reklaw, Carrizo.
Its lease has reported 193K barrels of oil and 135K mcf of gas since June 2014, last reporting volume in August 2026.
Operator of record
- 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 schedule | EOG Resources Inc. |
| Production reports | EOG Resources, Inc.through Aug 2026 |
| Latest permit | EOG Resources, Inc.May 23, 2014 |
- 9,876
- total depth, ft
- 1
- permits on file
- May 23, 2014
- last permit issued
- Jul 10, 2014
- completed
- 193K
- cumulative oil, bbl
- 135K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · JUN 2014 THROUGH AUG 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 10, 2014
- 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.
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Daly Unit O-1-17847 | Eagleville (Eagle Ford-1) | EOG Resources, Inc. | 1 | 193K | 135K | Jun 2014 – Aug 2026 |
Oil, barrels lease total
Last 12 months 5,355 · prior 12 5,572(-4%)
Gas, mcf lease total
Last 12 months 3,259 · prior 12 5,054(-36%)
Wells named Daly Unit
EOG Resources Inc.'s other wells filed under this lease name in Wilson 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 wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1EOG Resources, Inc.Jun 2014 → Aug 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 786804-99 | Drill | EOG Resources, Inc. | May 12, 2014 | May 23, 2014 | Jun 13, 2014 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jul 10, 2014 | Daly Unit O-1-17847 | Eagleville (Eagle Ford-1) | EOG Resources Inc. | Producing | 9,876 |
Formation tops
As filed on W-2/G-1. Subsea from 384 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Yegua | 1,024 | -640 |
| Queen City | 2,054 | -1,670 |
| Reklaw | 2,984 | -2,600 |
| Carrizo | 3,139 | -2,755 |
| WilcoxWILCOX - DISPOSAL | 4,354 | -3,970 |
| Navarro | 7,487 | -7,103 |
| BudaBUDA - H2S | — | — |
| EdwardsEDWARDS - H2S, DISPOSAL | — | — |
| GeorgetownGEORGETOWN - H2S | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,005 | 13,750 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 631 | 17.5 | 500 S |
| 9.625 | 5,950 | 12.25 | 1,870 S |
| 5.5 | 13,844 | 8.5 | 1,510 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Oct 22, 2014 | Aug 6, 2014 | Yes |
Well logs
1 log loaded from the RRC's log index, 1 of it with a digital LAS file, the latest received Jun 6, 2017. Gamma ray. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Gamma RaySpans Navarro | LAS + TIFF | 8,900 to 13,845 | Jun 6, 2017 | 0.59 + 1.41 |
"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.
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.
- Wellbore filings for 42-493-32792 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-493-32792 → scanned completion filings
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/49332792, documented in the API reference.