Long landing rollout — AAY877

KBLV · 32L

2026-08-20 20:58 UTC· KPGD → KBLV· ALLEGIANT AIR LLC· A320

▶ Replay 📊 Analyse

AAY877 (Allegiant AIR) was operating from KPGD to KBLV on 2026-08-20. SkyMeter detected a long landing rollout at Scott AFB/Midamerica Airport (KBLV) on runway 32L at 20:58 UTC. Trace data at the event: 442 ft AGL, 17 kt GS, 0 fpm vertical. METAR at the time reported 7 kt wind, 7 kt crosswind component, 9,994 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/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 →
  • UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

    Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6464 2026-08-20 13:30Z – 2026-08-20 21:00Z SFC–999 ft

    Destin, FL, Thursday, August 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 32L
  • 442 ft AGL at event
  • 17 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 7 kt crosswind component
  • 9,994 m visibility
  • KBLV 161455Z COR VRB03KT 9999 FEW060 BKN200 29/23 A3024 RMK AO2A SLP239 WND DATA ESTMD ALSTG/SLP ESTMD $ COR 1502

Flight context

  • AAY877
  • Allegiant AIR
  • A320
  • KPGD → KBLV
  • 2026-08-20 20:58 UTC
  • KBLV runway 32L

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