Diversion — AAY2560
KX06 · 142026-05-31 18:17 UTC· KPVD → KX06· SUNRISE ASSET MANAGEMENT LLC· A320
AAY2560 (Sunrise Asset Management) was operating from KPVD to KPGD (Charlotte County Airport) on 2026-05-31. SkyMeter detected a diversion to Arcadia Municipal Airport (KX06) on runway 14 at 18:17 UTC. Peak cruise altitude FL381, turnaround area near Pine Knoll Shores, US. Approach stability score: 31/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, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft
Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 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 31/100
- 5 kt wind
- 2 kt crosswind component
Flight context
- AAY2560
- Sunrise Asset Management
- A320
- KPVD → KX06
- 2026-05-31 18:17 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