Diversion — UAL372
KPWM · 112026-08-18 19:16 UTC· KDEN → KPWM· WILMINGTON TRUST COMPANY TRUSTEE· B39M
UAL372 (Wilmington Trust) was operating from KDEN to KEGE (Eagle County Regional Airport) on 2026-08-18. SkyMeter detected a diversion to Portland International Jetport (KPWM) on runway 11 at 19:16 UTC. Peak cruise altitude FL369, turnaround area near Hammond, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/2574 2026-08-13 12:00Z – 2026-08-24 05:00Z SFC–400 ft
des moines, IA, Thursday, August 13, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft
43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC
View FAA NOTAM → - SECURITY6/5108 2026-08-18 16:30Z – 2026-08-20 16:00Z SFC–17,999 ft
Des Moines, IA, Tuesday, August 18, 2026 through Thursday, August 20, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 11
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPWM 161451Z 24003KT 10SM FEW050 FEW110 19/12 A3031 RMK AO2 SLP265 T01890122 50002 $
Flight context
- UAL372
- Wilmington Trust
- B39M
- KDEN → KPWM
- 2026-08-18 19:16 UTC
- KPWM runway 11
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data