Long landing rollout — AAY2271

AAY2271 (Bank of Utah) was operating from KP19 to KGRI on 2026-08-21. SkyMeter detected a long landing rollout at Central Nebraska Regional Airport (KGRI) on runway 17 at 00:35 UTC. Trace data at the event: 1860 ft AGL, 0 kt GS. METAR at the time reported 11 kt wind, 4,023 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.

• HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

  20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2767 2026-08-07 12:00Z – 2026-08-21 04:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2768 2026-08-07 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

  8NM SW RIFLE, CO, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2913 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

  10NM SW RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2914 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–6,500 ft

  8NM W RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft

  28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3080 2026-08-08 22:15Z – 2026-08-22 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3097 2026-08-09 13:00Z – 2026-08-23 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3101 2026-08-09 13:00Z – 2026-08-24 03:00Z SFC–15,000 ft

  24NM SW PUEBLO, CO, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3679 2026-08-11 12:00Z – 2026-08-25 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3659 2026-08-11 13:00Z – 2026-08-24 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Tuesday, August 11, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4894 2026-08-13 13:00Z – 2026-08-28 04:00Z SFC–15,000 ft

  8NM SE TRINIDAD, CO, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5463 2026-08-17 13:00Z – 2026-08-30 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6712 2026-08-20 00:53Z – 2026-08-22 04:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 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.

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