Diversion — EJA400
KORD · 09L2026-07-19 23:57 UTC· KCMH → KORD· NETJETS SALES INC· E55P
EJA400 (Netjets Sales) was operating from KCMH to KORD (Chicago O'Hare International Airport) on 2026-07-19. SkyMeter detected a diversion to Chicago O'Hare International Airport (KORD) on runway 09L at 23:57 UTC. Peak cruise altitude FL316, turnaround area near Andrews, US. Approach stability score: 95/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 9 kt wind, 7 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)- SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Westfield, IN
View FAA NOTAM → - SECURITY6/7194 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Columbus, OH
View FAA NOTAM → - SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft
Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 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 09L
- 664 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 95/100
- 9 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KORD 180451Z 04012KT 10SM BKN012 BKN018 OVC030 20/17 A3025 RMK AO2 SLP240 T02000172
Flight context
- EJA400
- Netjets Sales
- E55P
- KCMH → KORD
- 2026-07-19 23:57 UTC
- KORD runway 09L
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