Diversion — AAY600
KX06 · 142026-06-14 22:36 UTC· KIND → KX06· ALLEGIANT AIR LLC· A320
AAY600 (Allegiant AIR) was operating from KIND to KPGD (Charlotte County Airport) on 2026-06-14. SkyMeter detected a diversion to Arcadia Municipal Airport (KX06) on runway 14 at 22:36 UTC. Peak cruise altitude FL394, turnaround area near Lovejoy, US. Approach stability score: 38/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, 4 kt crosswind component. 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/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
TAMPA, FL, 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 → - HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/5785 2026-06-11 18:00Z – 2026-06-15 04:00Z SFC–400 ft
Manchester, TN, Thursday, June 11, 2026 through Monday, June 15, 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 14
- 58 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 38/100
- 6 kt wind
- 4 kt crosswind component
Flight context
- AAY600
- Allegiant AIR
- A320
- KIND → KX06
- 2026-06-14 22:36 UTC
- KX06 runway 14
All events on this flight
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