Unstable approach — SWA550

KMQY · 14

2026-07-17 13:24 UTC· KMCO KMQY· UMB BANK NA TRUSTEE· B738

SWA550 (UMB Bank NA) was operating from KMCO to KMQY on 2026-07-17. SkyMeter detected a low approach-stability score at Smyrna Airport (KMQY) on runway 14 at 13:24 UTC. Trace data at the event: 1637 ft AGL, 143 kt GS. Approach stability score: 37/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, 1 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/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Nashville, TN

    View FAA NOTAM →
  • SECURITY6/7600 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft

    Chattanooga, TN

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

    Atlanta, GA

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

    Marietta, GA

    View FAA NOTAM →
  • HAZARDS6/4885 2026-07-11 11:00Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4910 2026-07-11 11:33Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/5640 2026-07-15 12:30Z – 2026-07-18 06:00Z SFC–2,500 ft

    MAYPORT, FL, Wednesday, July 15, 2026 through Saturday, July 18, 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 14
  • 1637 ft AGL at event
  • 143 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 3 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KMQY 162256Z 08004KT 10SM SCT070 34/21 A3025 RMK AO2 SLP243 T03390206 $

Flight context

  • SWA550
  • UMB Bank NA
  • B738
  • KMCO → KMQY
  • 2026-07-17 13:24 UTC
  • KMQY runway 14

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· KMQY