Unstable approach — FFT9531

US-3224 · 9W

2026-06-29 03:13 UTC· N85 → ?· UMB BANK NA TRUSTEE· A20N

FFT9531 (UMB Bank NA) had departed N85 on 2026-06-29. SkyMeter detected a low approach-stability score at US-3224 (US-3224) on runway 9W at 03:13 UTC. Trace data at the event: 1093 ft AGL, 117 kt GS. Approach stability score: 35/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 3 kt wind, 3 kt crosswind component. 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/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9498 2026-06-24 11:00Z – 2026-06-30 23:59Z SFC–2,000 ft

    Baltimore, MD, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/1007 2026-06-29 02:15Z – 2026-06-29 07:04Z SFC–180 ft

    Cape Canaveral, FL, Sunday, June 28, 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 9W
  • 1093 ft AGL at event
  • 117 kt ground speed
  • 0 fpm vertical
  • Approach stability 35/100
  • 3 kt wind
  • 3 kt crosswind component

Flight context

  • FFT9531
  • UMB Bank NA
  • A20N
  • 2026-06-29 03:13 UTC
  • US-3224 runway 9W

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· US-3224