Long landing rollout — TKR210

TKR210 (CSC Delaware Trust) was operating from KRDM to ID92 on 2026-07-28. SkyMeter detected a long landing rollout at Foster Field - Dzone Skydiving Airport (ID92) on runway 23 at 02:58 UTC. Trace data at the event: 2857 ft AGL, 13 kt GS. METAR at the time reported 7 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.

• HAZARDS6/6100 2026-07-16 14:00Z – 2026-07-30 04:00Z SFC–10,000 ft

  41NM SE BURNS, OR, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6453 2026-07-17 15:04Z – 2026-08-01 04:00Z SFC–9,000 ft

  26NM NW RILEY, OR, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6454 2026-07-17 15:06Z – 2026-07-31 04:00Z SFC–9,000 ft

  10NM N RILEY, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6572 2026-07-18 03:14Z – 2026-07-31 04:00Z SFC–11,000 ft

  18NM SE PRINEVILLE, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6812 2026-07-19 23:08Z – 2026-08-03 03:00Z SFC–11,000 ft

  23NM SE PRINEVILLE, OR, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6855 2026-07-20 01:34Z – 2026-08-03 03:00Z SFC–11,000 ft

  45NM NW BURNS, OR, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

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

  4NM NE BOISE, ID, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8112 2026-07-23 17:45Z – 2026-08-06 04:00Z SFC–11,000 ft

  45NM NW BURNS, OR, Thursday, July 23, 2026 through Thursday, August 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8435 2026-07-24 18:00Z – 2026-08-07 04:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8481 2026-07-24 22:00Z – 2026-08-08 05:00Z SFC–11,500 ft

  57NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8546 2026-07-25 17:15Z – 2026-08-09 05:00Z SFC–10,000 ft

  10NM NW BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8553 2026-07-25 17:30Z – 2026-08-09 04:00Z SFC–11,500 ft

  44NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8556 2026-07-25 19:00Z – 2026-08-09 05:00Z SFC–10,000 ft

  10NM NW BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8562 2026-07-25 21:00Z – 2026-08-09 05:00Z SFC–10,000 ft

  50NM W JOHN DAY, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8654 2026-07-26 16:00Z – 2026-08-10 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8761 2026-07-26 16:30Z – 2026-08-09 05:00Z SFC–11,500 ft

  50NM SE BURNS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8762 2026-07-26 17:00Z – 2026-08-10 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8784 2026-07-26 18:45Z – 2026-08-10 05:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9354 2026-07-27 22:15Z – 2026-08-10 05:00Z SFC–10,000 ft

  26NM S BURNS, OR, Monday, July 27, 2026 through Monday, August 10, 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