Long landing rollout — AAY1482
KVPS · 302026-07-17 03:36 UTC· KSGF → KVPS· SUNRISE ASSET MANAGEMENT LLC· A320
AAY1482 (Sunrise Asset Management) was operating from KSGF to KVPS on 2026-07-17. SkyMeter detected a long landing rollout at Destin-Ft Walton Beach Airport (KVPS) on runway 30 at 03:36 UTC. Trace data at the event: 95 ft AGL, 16 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 1 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4119 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/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/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
View FAA NOTAM → - SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
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 30
- 95 ft AGL at event
- 16 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KVPS 170155Z 06004KT 10SM CLR 29/22 A3021 RMK AO2A SLPNO ALSTG ESTMD FZRANO $
Flight context
- AAY1482
- Sunrise Asset Management
- A320
- KSGF → KVPS
- 2026-07-17 03:36 UTC
- KVPS runway 30
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