Long landing rollout — AAY508

KBLV · 32R

2026-09-04 18:12 UTC· KFLL KBLV· ALLEGIANT AIR LLC· B38M

AAY508 (Allegiant AIR) was operating from KFLL to KBLV on 2026-09-04. SkyMeter detected a long landing rollout at Scott AFB/Midamerica Airport (KBLV) on runway 32R at 18:12 UTC. Trace data at the event: 436 ft AGL, 6 kt GS, 0 fpm vertical. Approach stability score: 80/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 kt wind, 4 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • 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 →

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 32R
  • 436 ft AGL at event
  • 6 kt ground speed
  • 0 fpm vertical
  • Approach stability 80/100
  • 6 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KBLV 161855Z 20006KT 10SM SCT060 BKN200 35/25 A3020 RMK AO2A SLP225 T03490248 $

Flight context

  • AAY508
  • Allegiant AIR
  • B38M
  • KFLL → KBLV
  • 2026-09-04 18:12 UTC
  • KBLV runway 32R

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