WELL · 42-383-42235 · DISTRICT 9

UL Victorio East C 5-8-17 #503UH

N

Reagan County  · Horizontal

UL Victorio East C 5-8-17 #503UH (API 42-383-42235) is a permitted horizontal well in Reagan County filed by Iron Orchard Operating LLC; no completion report is on file yet.

The RRC has issued one drilling permit (amended once), issued November 21, 2025, permitted to 9,000 ft.

Operator of record

Iron Orchard Operating LLC

Houston, TX · P-5 Y, filed Mar 4, 2026 · 65 permits on file · (844) 523-2014

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitIron Orchard Operating LLCNov 21, 2025
9,000
total depth, ft
2
permits on file
Nov 21, 2025
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

31.137103, -101.744743

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Reagan County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
911780-98DrillIron Orchard Operating LLCApr 7, 2026Nov 21, 2025—9,000
911780-99DrillIron Orchard Operating LLCNov 14, 2025Nov 21, 2025—9,000

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

University West42-383-40019

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Yates1,804905
Queen2,64465
Grayburg3,037-328
San Andres3,692-983
Clear Fork5,443-2,734
Spraberry6,034-3,325
Wolfcamp7,453-4,744
Ellenburger—

10 TOPS · FIRST 8

University West42-383-40020

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Yates1,803906
Queen2,65554
Grayburg3,044-335
San Andres3,700-991
Clear Fork5,438-2,729
Spraberry6,037-3,328
Wolfcamp7,458-4,749
Fusselman—

10 TOPS · FIRST 8

University West42-383-40021

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Strawn—
Clear Fork—
Ellenburger—
Fusselman—
Grayburg—
Queen—
San Andres—
Spraberry—

University West42-383-40022

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Spraberry—
Clear Fork—
Ellenburger—
Fusselman—
Grayburg—
Queen—
San Andres—
Strawn—

University West42-383-40023

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Clear Fork—
Ellenburger—
Fusselman—
Grayburg—
Queen—
San Andres—
Spraberry—
Strawn—

University West42-383-40024

1.6 KM · EP Energy E&P Company, L.P. · Section with this well →

Clear Fork—
Ellenburger—
Fusselman—
Grayburg—
Queen—
San Andres—
Spraberry—
Strawn—

University 1-3242-383-41043

3.2 KM · Pioneer Natural Res. USA, Inc. · Section with this well →

Queen2,904-78
Grayburg3,416-590
San Andres3,757-931
Clear Fork5,476-2,650
Spraberry6,252-3,426
Fusselman—
Ellenburger—
Strawn—

University 4-3042-461-38786

3.2 KM · Apache Corporation · Section with this well →

Spraberry6,222-3,513
UP Spraberry6,222-3,513
Spraberry6,827-4,118
Lo. Spraberry 68276,827-4,118
Dean7,490-4,781
Wolfcamp7,618-4,909
Strawn9,290-6,581
Atoka9,733-7,024

9 TOPS · FIRST 8

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