Long landing rollout — AAY3152
5AZ3 · 262026-05-20 15:14 UTC· KFNT → 5AZ3· ALLEGIANT AIR LLC· A320
AAY3152 (Allegiant AIR) was operating from KFNT to 5AZ3 on 2026-05-20. SkyMeter detected a long landing rollout at Pegasus Airpark (5AZ3) on runway 26 at 15:14 UTC. Trace data at the event: 1345 ft AGL, 7 kt GS. METAR at the time reported 2 kt wind, 2 kt crosswind component. 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/9663 2026-05-12 13:00Z – 2026-05-26 03:00Z SFC–10,500 ft
38NM NW SILVER CITY, NM, Tuesday, May 12, 2026 through Tuesday, May 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft
22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft
19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft
5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/1337 2026-05-19 01:30Z – 2026-05-21 01:30Z SFC–6,000 ft
9NM NW ASHLAND, KS, Tuesday, May 19, 2026 through Thursday, May 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/1338 2026-05-19 01:30Z – 2026-05-21 01:30Z SFC–6,000 ft
4NM SE MEADE, KS, Tuesday, May 19, 2026 through Thursday, May 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 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 26
- 1345 ft AGL at event
- 7 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 2 kt crosswind component
Flight context
- AAY3152
- Allegiant AIR
- A320
- KFNT → 5AZ3
- 2026-05-20 15:14 UTC
- 5AZ3 runway 26
All events on this flight
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