Long landing rollout — AAY1003
KPIE · 17L2026-07-28 02:32 UTC· KATW → KPIE· ALLEGIANT AIR LLC· B38M
AAY1003 (Allegiant AIR) was operating from KATW to KPIE on 2026-07-28. SkyMeter detected a long landing rollout at St Petersburg Clearwater International Airport (KPIE) on runway 17L at 02:32 UTC. Trace data at the event: 13 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 91/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 5 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)- HAZARDS6/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft
16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7614 2026-07-27 20:30Z – 2026-07-28 03:59Z SFC–400 ft
Atlanta, GA, Monday, July 27, 2026 through Tuesday, July 28, 2026 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 17L
- 13 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 91/100
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KPIE 171353Z 06008KT 10SM CLR 28/23 A3014 RMK AO2 SLP207 T02780228
Flight context
- AAY1003
- Allegiant AIR
- B38M
- KATW → KPIE
- 2026-07-28 02:32 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