Long landing rollout — DAL2243

DAL2243 (Delta AIR Lines) was operating from KLAX to KMCI on 2026-08-28. SkyMeter detected a long landing rollout at Kansas City International Airport (KMCI) on runway 09 at 04:24 UTC. Trace data at the event: 990 ft AGL, 22 kt GS. METAR at the time reported 4 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.

• 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/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/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 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/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

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

  41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7117 2026-08-23 11:00Z – 2026-08-29 01:00Z SFC–13,500 ft

  30NM SW PUEBLO, CO, Sunday, August 23, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft

  26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7422 2026-08-24 14:30Z – 2026-09-08 05:00Z SFC–12,500 ft

  26NM NE RUIDOSO, NM, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC

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

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

  View FAA NOTAM →
• HAZARDS6/7718 2026-08-25 14:00Z – 2026-09-08 04:00Z SFC–8,000 ft

  4.5 NM NE BAGDAD, AZ, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft

  21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8069 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–14,000 ft

  26NM SE ALBUQUERQUE, NM, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8420 2026-08-26 20:10Z – 2026-08-28 03:00Z SFC–15,000 ft

  35NM SW ALAMOSA, CO, Wednesday, August 26, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8502 2026-08-27 14:00Z – 2026-09-09 03:00Z SFC–15,000 ft

  48NM NW TAOS, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8586 2026-08-27 17:30Z – 2026-08-28 04:00Z SFC–14,000 ft

  24NM SE ALBUQUERQUE, NM, Thursday, August 27, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8590 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8591 2026-08-27 18:15Z – 2026-08-29 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Thursday, August 27, 2026 through Saturday, August 29, 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