Go-around — AAL2933

KORD · 09L

2026-06-28 17:28 UTC· KPDX KORD· BANK OF UTAH TRUSTEE· B738

AAL2933 (Bank of Utah) was operating from KPDX to KORD on 2026-06-28. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 09L at 17:28 UTC. Trace data at the event: 830 ft AGL, 152 kt GS. METAR at the time reported 9 kt wind, 3 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/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

    MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4159 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

    Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft

    3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9121 2026-06-18 13:00Z – 2026-07-01 05:00Z SFC–7,000 ft

    10NM SE PENDLETON, OR, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9554 2026-06-22 13:00Z – 2026-07-06 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Monday, July 6, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9557 2026-06-22 13:00Z – 2026-07-07 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Tuesday, July 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0613 2026-06-25 13:00Z – 2026-07-08 03:00Z SFC–14,500 ft

    27NM SW JACKSON, WY, Thursday, June 25, 2026 through Wednesday, July 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0606 2026-06-25 14:00Z – 2026-07-10 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0614 2026-06-25 14:00Z – 2026-07-10 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1022 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1023 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft

    37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC

    View FAA NOTAM →
  • SPACE OPERATIONS6/1188 2026-06-28 15:00Z – 2026-06-28 21:00Z SFC–10,000 ft

    88 ZSE AIRSPACE BROTHERS, OR, Sunday, June 28, 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
  • 830 ft AGL at event
  • 152 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KORD 171751Z 33005KT 10SM BKN014 BKN025 BKN150 BKN250 25/22 A3018 RMK AO2 SLP218 60037 T02500217 10256 20194 58008

Flight context

  • AAL2933
  • Bank of Utah
  • B738
  • KPDX → KORD
  • 2026-06-28 17:28 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

SkyMeter · trace data observed via ADS-B· KORD