Long landing rollout — AAY931

KPGD · 22

2026-01-31 02:07 UTC· KSWF → KPGD· ALLEGIANT AIR LLC· A320

AAY931 (Allegiant AIR) was operating from KSWF to KPGD on 2026-01-31. SkyMeter detected a long landing rollout at Charlotte County Airport (KPGD) on runway 22 at 02:07 UTC. Trace data at the event: 26 ft AGL, 11 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 3 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)
  • 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 →

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 22
  • 26 ft AGL at event
  • 11 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KPGD 251453Z 06011KT 10SM SCT016 26/21 A3000 RMK AO2 SLP158 T02560211 51004 $

Flight context

  • AAY931
  • Allegiant AIR
  • A320
  • KSWF → KPGD
  • 2026-01-31 02:07 UTC
  • KPGD runway 22

All events on this flight

Long landing rollout 02:07:37 UTC · KPGD runway 22 · 26 ft AGL · 11 kt GS
Long landing rollout 02:07:37 UTC · KPGD runway 22 · 26 ft AGL · 11 kt GS
Long landing rollout 02:07:37 UTC · KPGD runway 22 · 26 ft AGL · 11 kt GS
Long landing rollout 02:07:37 UTC · KPGD runway 22 · 26 ft AGL · 11 kt GS

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