Long landing rollout — AAY261

KPIE · 17L

2026-07-11 01:02 UTC· KAVL KPIE· ALLEGIANT AIR LLC· A320

AAY261 (Allegiant AIR) was operating from KAVL to KPIE on 2026-07-11. SkyMeter detected a long landing rollout at St Petersburg Clearwater International Airport (KPIE) on runway 17L at 01:02 UTC. Trace data at the event: 13 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 5 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)
  • SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7594 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft

    Atlanta, GA

    View FAA NOTAM →
  • SECURITY6/7597 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft

    Marietta, GA

    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 17L
  • 13 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KPIE 180453Z AUTO 05008KT 10SM CLR 26/22 A3010 RMK AO2 SLP192 T02610217 403280250

Flight context

  • AAY261
  • Allegiant AIR
  • A320
  • KAVL → KPIE
  • 2026-07-11 01:02 UTC
  • KPIE runway 17L

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