Long landing rollout — AAY193
KPIE · 35R2026-07-11 14:40 UTC· KABE → KPIE· ALLEGIANT AIR LLC· A320
AAY193 (Allegiant AIR) was operating from KABE to KPIE on 2026-07-11. SkyMeter detected a long landing rollout at St Petersburg Clearwater International Airport (KPIE) on runway 35R at 14:40 UTC. Trace data at the event: 13 ft AGL, 13 kt GS, 0 fpm vertical. METAR at the time reported 2 kt wind, 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/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, 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/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV
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/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC
View FAA NOTAM → - AIR SHOWS/SPORTS6/3030 2026-07-10 21:00Z – 2026-07-12 19:00Z SFC–4,000 ft
Sparrows Point, MD, Friday, July 10, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - SPACE OPERATIONS6/3766 2026-07-11 08:10Z – 2026-07-11 13:02Z SFC–180 ft
Cape Canaveral, FL, Saturday, July 11, 2026 Local
View FAA NOTAM → - HAZARDS6/4885 2026-07-11 11:00Z – 2026-07-20 01:00Z SFC–5,000 ft
14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - VIP6/4386 2026-07-11 11:30Z – 2026-07-11 23:30Z SFC–9,999 ft
Sterling, VA, Saturday, July 11, 2026 Local
View FAA NOTAM → - HAZARDS6/4910 2026-07-11 11:33Z – 2026-07-20 01:00Z SFC–5,000 ft
14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 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 35R
- 13 ft AGL at event
- 13 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPIE 152053Z 01004KT 10SM CLR 31/22 A3002 RMK AO2 SLP165 T03110217 56012
Flight context
- AAY193
- Allegiant AIR
- A320
- KABE → KPIE
- 2026-07-11 14:40 UTC
- KPIE runway 35R
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