Unstable approach — AAL3330

KORD · 28L

2026-07-05 17:58 UTC· KDFW KORD· BANK OF UTAH TRUSTEE· A321

AAL3330 (Bank of Utah) was operating from KDFW to KORD on 2026-07-05. SkyMeter detected a low approach-stability score at Chicago O'Hare International Airport (KORD) on runway 28L at 17:58 UTC. Trace data at the event: 1796 ft AGL, 153 kt GS. Approach stability score: 47/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 7 kt wind, 7 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft

    DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

    TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

    St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/1457 2026-07-01 11:00Z – 2026-07-06 02:00Z SFC–400 ft

    SILVIS, IL, Wednesday, July 1, 2026 through Sunday, July 5, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7652 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Riverside, MO

    View FAA NOTAM →
  • SECURITY6/7650 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Kansas City, MO

    View FAA NOTAM →
  • SECURITY6/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Frisco, TX

    View FAA NOTAM →
  • SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Frisco, TX

    View FAA NOTAM →
  • SECURITY6/1428 2026-07-03 05:01Z – 2026-07-06 04:59Z SFC–1,000 ft

    Kansas City, MO, Friday, July 3, 2026 through Sunday, July 5, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7646 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Lawrence, KS

    View FAA NOTAM →
  • SECURITY6/7647 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Lawrence, KS

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1390 2026-07-03 19:00Z – 2026-07-06 02:00Z SFC–5,000 ft

    mattoon, IL, Friday, July 3, 2026 through Monday, July 6, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/1406 2026-07-05 16:00Z – 2026-07-05 21:00Z SFC–400 ft

    Joliet, IL, Sunday, July 5, 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 28L
  • 1796 ft AGL at event
  • 153 kt ground speed
  • 0 fpm vertical
  • Approach stability 47/100
  • 7 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KORD 170051Z 02009KT 10SM BKN007 OVC015 19/18 A3028 RMK AO2 SLP251 T01940178 $

Flight context

  • AAL3330
  • Bank of Utah
  • A321
  • KDFW → KORD
  • 2026-07-05 17:58 UTC
  • KORD runway 28L

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