WELL · 42-475-38925 · DISTRICT 10

Fat Man 99-82 #502H

N

Ward County  · Horizontal

Fat Man 99-82 #502H (API 42-475-38925) is a permitted horizontal well in Ward County filed by Iron Orchard Operating LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued February 13, 2025, permitted to 15,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 LLCFeb 13, 2025
15,000
total depth, ft
1
permits on file
Feb 13, 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.550565, -103.135045

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Ward 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
905367-99DrillIron Orchard Operating LLCJan 20, 2025Feb 13, 2025—15,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 →

Utl Wild Bunch 0135A42-475-38974

0.9 KM · Continental Resources, Inc. · Section with this well →

Seven Rivers—
Capitan—
Clear Fork—
Delaware—
Glorieta—
Holt—
Yates—
Queen—

10 TOPS · FIRST 8

Woodberry 342-475-37766

1.0 KM · Abraxas Petroleum Corporation · Section with this well →

Rustler2,000653
Bone Spring8,038-5,385
Bone Spring8,976-6,323
Bone Spring9,935-7,282
San Andres—
Queen—
Holt—
Glorieta—

10 TOPS · FIRST 8

Woodberry 342-475-37767

1.1 KM · Abraxas Petroleum Corporation · Section with this well →

Rustler2,000653
Delaware4,880-2,227
Clear Fork—
Holt—
Queen—
San Andres—
Seven Rivers—
Tubb—

10 TOPS · FIRST 8

UL McNasser 0201-1742-475-38152

1.1 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon4,900-2,224
Cherry Canyon6,107-3,431
Brushy Canyon7,030-4,354
Bone Spring8,097-5,421
Rustler—
Capitan—
Clear Fork—
Delaware—

15 TOPS · FIRST 8

UL McNasser 0201-1742-475-38151

1.1 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon4,900-2,228
Cherry Canyon6,078-3,406
Brushy Canyon7,003-4,331
Bone Spring8,059-5,387
Capitan—
Delaware—
Clear Fork—
Yates—

15 TOPS · FIRST 8

UL McNasser 0201-1742-475-38146

1.1 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon4,902-2,230
Cherry Canyon6,088-3,416
Brushy Canyon7,011-4,339
Bone Spring8,063-5,391
Wolfcamp10,989-8,317
Clear Fork—
Tubb—
Seven Rivers—

18 TOPS · FIRST 8

UL McNasser 0201-1742-475-38147

1.1 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon4,900-2,228
Cherry Canyon6,098-3,426
Brushy Canyon7,023-4,351
Bone Spring7,105-4,433
Wolfcamp11,056-8,384
Queen—
Precambrian (Undifferentiated)—
Clear Fork—

17 TOPS · FIRST 8

UL McNasser 0201-1742-475-38148

1.2 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon4,900-2,227
Cherry Canyon6,112-3,439
Brushy Canyon7,047-4,374
Bone Spring8,127-5,454
Wolfcamp11,073-8,400
Seven Rivers—
Yates—
Red Bluff—

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