Diversion — UAL2401
KLOT · 092026-08-21 20:27 UTC· KORD → KLOT· UNITED AIRLINES INC· B739
UAL2401 (United Airlines) was operating from KORD to MYNN (Lynden Pindling International Airport) on 2026-08-21. SkyMeter detected a diversion to Lewis University Airport (KLOT) on runway 09 at 20:27 UTC. Peak cruise altitude FL365, turnaround area near Portland, US. METAR at the time reported 8 kt wind, 6 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- UAS PUBLIC GATHERING6/5500 2026-08-21 16:00Z – 2026-08-22 04:00Z
DETROIT, MI, Friday, August 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/5504 2026-08-21 16:00Z – 2026-08-22 04:00Z SFC–400 ft
Detroit, MI, Friday, August 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/5866 2026-08-21 16:00Z – 2026-08-22 06:00Z SFC–400 ft
Detroit, MI, Friday, August 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/6868 2026-08-21 16:00Z – 2026-08-22 06:00Z SFC–400 ft
Detroit, MI, Friday, August 21, 2026 through Saturday, August 22, 2026 UTC
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 09
- 666 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- METAR KLOT 152145Z 30003KT 10SM FEW055 BKN120 28/26 A3007
Flight context
- UAL2401
- United Airlines
- B739
- KORD → KLOT
- 2026-08-21 20:27 UTC
- KLOT runway 09
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