Diversion — AAY2531

KX06 · 14

2026-08-02 16:32 UTC· KMDW → KX06· ALLEGIANT AIR LLC· A320

▶ Replay 📊 Analyse

AAY2531 (Allegiant AIR) was operating from KMDW to KPGD (Charlotte County Airport) on 2026-08-02. SkyMeter detected a diversion to Arcadia Municipal Airport (KX06) on runway 14 at 16:32 UTC. Peak cruise altitude FL384, turnaround area near Bartow, US. 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 5 kt wind, 3 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/0628 2026-07-31 13:07Z – 2026-08-03 01:30Z SFC–1,300 ft

    13NM S TAYLOR, FL, Friday, July 31, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • 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 →
  • SECURITY6/0650 2026-08-01 16:00Z – 2026-08-02 22:00Z SFC–400 ft

    Michigan City, IN, Saturday, August 1, 2026 through Sunday, August 2, 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
  • 58 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 5 kt wind
  • 3 kt crosswind component

Flight context

  • AAY2531
  • Allegiant AIR
  • A320
  • KMDW → KX06
  • 2026-08-02 16:32 UTC
  • KX06 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· KX06