TEXAS · WELLS · IRION COUNTY · API 42-235-35139 · DISTRICT 6E

Cortes #1H

Y

Irion County · Spraberry (Trend Area) field · Producing  · Horizontal

Cortes #1H (API 42-235-35139) is a horizontal well in Irion County operated by Permian Resources Operating LLC, completed December 13, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 23, 2012, permitted to 6,344 ft.

It was permitted by Devon Energy Production CO, L.P. and has since transferred to Permian Resources Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Spraberry, Dean, Wolfcamp.

Its 2 leases have reported 1.49M barrels of oil and 34.8M mcf of gas since December 2012, last reporting volume in April 2026. The leases carry 58 wells, so these are lease totals, not this well alone.

Operator of record

Permian Resources Operating LLC

Permitted by Devon Energy Production Co, L.P.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Nov 25, 2025
Permits on file
608
Phone
(432) 695-4222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePermian Resources Operating LLC
Production reportsPermian Resources Operating, LLCthrough Apr 2026
Latest permitDevon Energy Production Co, L.P.Aug 23, 2012

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

6,344
total depth, ft
1
permits on file
Aug 23, 2012
last permit issued
Dec 13, 2012
completed
1.49M
cumulative oil, bbl
34.8M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2012 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 13, 2012
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.

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cortes O-9-20552Spraberry (Trend Area)Permian Resources Operating, LLC30100K13MMar 2020 – Apr 2026
Cortes O-9-18117Lin (Wolfcamp)Sable Permian Resources, LLC281.39M21.8MDec 2012 – Feb 2020

Gas, mcf lease total

Last 12 months 1,470,236 · prior 12 1,895,792(-22%)

0100K200K300K202420252026

Oil, barrels lease total

Last 12 months 6,821 · prior 12 11,929(-43%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Devon Energy Production Co, L.P.Dec 2012 → Jul 2016
  2. 2FDL Operating, LLCAug 2016 → Apr 2022
  3. 3Sable Permian Resources Land,llcOct 2018 → Dec 2018
  4. 4Sable Permian Resources, LLCJan 2019 → Jan 2021
  5. 5Earthstone Operating, LLCMay 2022 → Oct 2023
  6. 6Permian Resources Operating, LLCNov 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
746506-99DrillDevon Energy Production Co, L.P.Aug 15, 2012Aug 23, 2012Sep 23, 20129,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 13, 2012Cortes O-9-20552Spraberry (Trend Area)Permian Resources Operating LLCProducing6,344
Dec 13, 2012Cortes O-9-18117Lin (Wolfcamp)Sable Permian Resources LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
SpraberryLOWER SPRABERRY4,966-2,382
Dean5,805-3,221
Wolfcamp5,939-3,355

Perforations

Perforated and open-hole intervals.

FromToType
6,61412,757Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,49012.25454 S
5.512,8538.752,585 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
00Feb 14, 2020Jan 30, 2013Yes
00Nov 14, 2013Jan 30, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Dec 26, 2013. Density, Neutron. 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
NEUTRON/DENSITY POROSITYSpans Spraberry, Dean, WolfcampTIFF1,489 to 8,200Dec 26, 2013run Nov 11, 20125.33

"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. The University Lands library has no per-well link: then paste it into its 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/23535139, documented in the API reference.