Long landing rollout — AAY1563

5AZ3 · 08

2026-05-26 16:47 UTC· KATW 5AZ3· UMB BANK NA TRUSTEE· A320

AAY1563 (UMB Bank NA) was operating from KATW to 5AZ3 on 2026-05-26. SkyMeter detected a long landing rollout at Pegasus Airpark (5AZ3) on runway 08 at 16:47 UTC. Trace data at the event: 1345 ft AGL, 7 kt GS. METAR at the time reported 6 kt wind, 5 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/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/0835 2026-05-16 12:00Z – 2026-05-28 05:00Z SFC–12,500 ft

    JACKSON, WY, Saturday, May 16, 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/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 →
  • HAZARDS6/2354 2026-05-22 12:00Z – 2026-06-04 04:00Z SFC–15,500 ft

    22NM NE RUIDOSO, NM, Friday, May 22, 2026 through Thursday, June 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft

    22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2212 2026-05-26 13:00Z – 2026-05-26 20:00Z SFC–2,000 ft

    MILTON, IL, Tuesday, May 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2213 2026-05-26 13:00Z – 2026-05-26 20:00Z SFC–2,000 ft

    HARRISBURG, MO, Tuesday, May 26, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/2624 2026-05-26 15:00Z – 2026-05-27 20:00Z SFC–1,000 ft

    KANSAS CITY, MO, Tuesday, May 26, 2026 through Wednesday, May 27, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/2449 2026-05-26 16:00Z – 2026-05-26 19:00Z SFC–2,000 ft

    PRESTON, KS, Tuesday, May 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2450 2026-05-26 16:00Z – 2026-05-26 19:00Z SFC–2,000 ft

    LANGDON, KS, Tuesday, May 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2451 2026-05-26 16:00Z – 2026-05-26 19:00Z SFC–2,000 ft

    ARLINGTON, KS, Tuesday, May 26, 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 08
  • 1345 ft AGL at event
  • 7 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 5 kt crosswind component

Flight context

  • AAY1563
  • UMB Bank NA
  • A320
  • KATW → 5AZ3
  • 2026-05-26 16:47 UTC
  • 5AZ3 runway 08

All events on this flight

Long landing rollout 16:47:23 UTC · 5AZ3 runway 08 · 1,345 ft AGL · 7 kt GS
Long landing rollout 16:47:23 UTC · 5AZ3 runway 08 · 1,345 ft AGL · 7 kt GS

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

SkyMeter · trace data observed via ADS-B· 5AZ3