Long landing rollout — EJM32

EJM32 (JMT II) was operating from KBLM to KJAC on 2026-08-02. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 19 at 19:05 UTC. Trace data at the event: 6397 ft AGL, 17 kt GS. Approach stability score: 89/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 6 kt wind, 5 kt crosswind component, 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/6894 2026-07-20 14:02Z – 2026-08-03 04:00Z SFC–12,500 ft

  12NM NW CRAIG, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6900 2026-07-20 14:42Z – 2026-08-03 04:00Z SFC–13,500 ft

  11NM SW KREMMLING, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

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

  7NM SE STEAMBOAT SPRINGS, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

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

  11NM SW CRAIG, CO, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7538 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–16,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7540 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–16,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8398 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8401 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8368 2026-07-29 19:00Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Wednesday, July 29, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8379 2026-07-29 19:00Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Wednesday, July 29, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/8930 2026-07-30 16:00Z – 2026-08-03 03:00Z SFC–400 ft

  Chicago, IL, Thursday, July 30, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0567 2026-07-31 18:00Z – 2026-08-02 23:30Z SFC–2,000 ft

  Morristown, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/9922 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/9923 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• SECURITY6/0650 2026-08-01 16:00Z – 2026-08-02 22:00Z SFC–400 ft

  Michigan City, IN, Saturday, August 1, 2026 through Sunday, August 2, 2026 Local

  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