KLM611 was operating from EHAM to KORD on 2026-06-25. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 27C at 19:09 UTC. Trace data at the event: 965 ft AGL, 157 kt GS. METAR at the time reported 9 kt wind, 2 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3959 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Boston, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3963 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FOXBOROUGH, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3969 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Waltham, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6850 2026-06-12 04:01Z – 2026-06-28 03:59Z SFC–1,000 ft
Boston, MA, Friday, June 12, 2026 through Saturday, June 27, 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 27C
- 965 ft AGL at event
- 157 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KORD 172151Z 03013KT 10SM SCT009 BKN018 OVC040 22/20 A3017 RMK AO2 SLP213 T02220200
Flight context
- KLM611
- B78X
- EHAM → KORD
- 2026-06-25 19:09 UTC
- KORD runway 27C
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