Long landing rollout — AAY2605
KPIE · 17L2026-09-04 02:16 UTC· 0PS9 → KPIE· ALLEGIANT AIR LLC· B38M
AAY2605 (Allegiant AIR) was operating from 0PS9 to KPIE on 2026-09-04. SkyMeter detected a long landing rollout at St Petersburg Clearwater International Airport (KPIE) on runway 17L at 02:16 UTC. Trace data at the event: 13 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 73/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 8 kt wind, 5 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)- UAS PUBLIC GATHERING6/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft
Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC
View FAA NOTAM → - SECURITY6/9130 2026-09-01 12:30Z – 2026-09-04 06:00Z SFC–2,500 ft
MAYPORT, FL, Tuesday, September 1, 2026 through Friday, September 4, 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 17L
- 13 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 73/100
- 8 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- METAR KPIE 252253Z 34011KT 10SM CLR 26/20 A2992 RMK AO2 SLP132 T02610200
Flight context
- AAY2605
- Allegiant AIR
- B38M
- 0PS9 → KPIE
- 2026-09-04 02:16 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