Diversion — UAL2616

9NC0 · 01

2026-08-26 17:37 UTC· KORD → 9NC0· UMB BANK NA TRUSTEE· A319

▶ Replay 📊 Analyse

UAL2616 (UMB Bank NA) was operating from KORD to KRDU (Raleigh Durham International Airport) on 2026-08-26. SkyMeter detected a diversion to Raleigh East Airport (9NC0) on runway 01 at 17:37 UTC. Peak cruise altitude FL387, turnaround area near Vanceburg, US. Approach stability score: 36/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 6 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/7959 2026-08-26 17:00Z – 2026-08-26 20:00Z SFC–16,000 ft

    Bunker Hill, IN, Wednesday, August 26, 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 01
  • 313 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 36/100
  • 6 kt wind
  • 2 kt crosswind component

Flight context

  • UAL2616
  • UMB Bank NA
  • A319
  • KORD → 9NC0
  • 2026-08-26 17:37 UTC
  • 9NC0 runway 01

All events on this flight

Diversion 17:37:00 UTC · 9NC0 runway 01 · 313 ft AGL · 120 kt GS
Unstable approach 17:34:35 UTC · 9NC0 runway 19 · 1,414 ft AGL · 137 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· 9NC0