WELL · 42-505-34723 · DISTRICT 4

Haynes #25

N

Zapata County  · Directional

Haynes #25 (API 42-505-34723) is a permitted well in Zapata County filed by Devon Energy Production CO, L.P.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 2003 and 2012, permitted to 15,500 ft.

Completion filings report 3 formation tops, including Wilcox, Lobo Unc., Lobo 6.

Operator of record

Devon Energy Production Co, L.P.

Oklahoma City, OK · P-5 Y, filed Nov 4, 2025 · 9,266 permits on file · (800) 465-8314

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsDevon Energy Production Co, L.P.through Feb 2012
Latest permitDevon Energy Production Co, L.P.Jan 19, 2012
15,500
total depth, ft
3
permits on file
Jan 19, 2012
last permit issued
—
completed
0
cumulative oil, bbl
668K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Haynes G-4-197019Munoz (Lobo)Hilcorp Energy Company10573KAug 2003 – Jul 2026
Haynes G-4-202920Comitas (Deep)Hilcorp Energy Company1094.6KJun 2004 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Legend Natural Gas, LPSep 2003 → Aug 2004
  2. 2Chesapeake Operating, Inc.Sep 2004 → Mar 2005
  3. 3Devon Energy Production Co, L.P.Mar 2005 → Feb 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
731219-99RecompletionDevon Energy Production Co, L.P.Jan 9, 2012Jan 19, 2012—15,022
547531-99RecompletionLegend Natural Gas, LPJun 28, 2004Jul 22, 2004Jun 1, 200415,022
531167-99DrillLegend Natural Gas, LPApr 28, 2003Apr 28, 2003Jun 6, 200315,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-197019————
—— G-4-202920————

Formation tops

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

FormationMD ftSubsea
Wilcox6,875-6,461
Lobo Unc.12,305-11,891
Lobo 614,345-13,931

Perforations

Perforated and open-hole intervals.

FromToType
8,9528,962Perforated
9,1189,126Perforated
9,1469,156Perforated
12,58412,394Perforated
12,58612,596Perforated
12,69312,703Perforated
12,97012,986Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,02417.5845 S
9.6256,49712.25460 S
79,8508.5515 S
4.515,0136.125740 S
4.515,0146.125740 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 29, 2006Nov 22, 2005—
00Oct 26, 2004Jul 14, 2004Yes
00Aug 24, 2004——
00Oct 24, 2003Sep 15, 2003Yes
00Oct 10, 2003——

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