Go-around — UAL2668

KORD · 09L

2026-08-17 13:58 UTC· KDSM → KORD· UMB BANK NA TRUSTEE· A319

▶ Replay 📊 Analyse

UAL2668 (UMB Bank NA) was operating from KDSM to KORD on 2026-08-17. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 09L at 13:58 UTC. Trace data at the event: 1362 ft AGL, 139 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component, 6,437 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)
  • 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 →

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
  • 1362 ft AGL at event
  • 139 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 5 kt crosswind component
  • 6,437 m visibility
  • KORD 162051Z 02008KT 4SM -RA BR BKN013 BKN022 OVC040 21/19 A3029 RMK AO2 RAB21 SLP254 P0001 60001 T02060189 58002 $

Flight context

  • UAL2668
  • UMB Bank NA
  • A319
  • KDSM → KORD
  • 2026-08-17 13:58 UTC
  • KORD runway 09L

All events on this flight

Go-around 13:58:15 UTC · KORD runway 09L · 1,362 ft AGL · 139 kt GS
Go-around 13:58:15 UTC · KORD runway 09L · 1,362 ft AGL · 139 kt GS

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

SkyMeter · trace data observed via ADS-B· KORD