Long landing rollout — AAY940
KPGD · 222026-06-26 04:00 UTC· KSBN → KPGD· ALLEGIANT AIR LLC· A320
AAY940 (Allegiant AIR) was operating from KSBN to KPGD on 2026-06-26. SkyMeter detected a long landing rollout at Charlotte County Airport (KPGD) on runway 22 at 04:00 UTC. Trace data at the event: 26 ft AGL, 3 kt GS, 0 fpm vertical. 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)- 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/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
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/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WESTFIELD, IN, 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/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft
Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local
View FAA NOTAM → - SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Carmel, IN
View FAA NOTAM → - SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Westfield, IN
View FAA NOTAM → - SECURITY6/9581 2026-06-25 04:01Z – 2026-06-26 03:59Z SFC–1,000 ft
Atlanta, GA, Thursday, June 25, 2026 through Thursday, June 25, 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 22
- 26 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- METAR KPGD 181653Z 06009KT 10SM FEW032 SCT060 BKN085 31/23 A3005 RMK AO2 SLP176 T03060228
Flight context
- AAY940
- Allegiant AIR
- A320
- KSBN → KPGD
- 2026-06-26 04:00 UTC
- KPGD runway 22
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