Long landing rollout — EJA656

EJA656 (Netjets Sales) was inbound to KS67 on 2026-07-23. SkyMeter detected a long landing rollout at Nampa Municipal Airport (KS67) on runway 11 at 00:25 UTC. Trace data at the event: 2506 ft AGL, 13 kt GS. METAR at the time reported 2 kt wind, 1 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/4238 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4242 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4239 2026-07-09 14:00Z – 2026-07-23 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4241 2026-07-09 14:00Z – 2026-07-23 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4548 2026-07-10 14:00Z – 2026-07-24 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4549 2026-07-10 14:00Z – 2026-07-24 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4968 2026-07-12 15:00Z – 2026-07-27 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Sunday, July 12, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4970 2026-07-12 15:00Z – 2026-07-27 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Sunday, July 12, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5879 2026-07-15 14:00Z – 2026-07-28 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Wednesday, July 15, 2026 through Tuesday, July 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5880 2026-07-15 14:00Z – 2026-07-29 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Wednesday, July 15, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6659 2026-07-18 14:00Z – 2026-07-31 10:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6660 2026-07-18 14:00Z – 2026-07-31 10:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6682 2026-07-18 16:49Z – 2026-07-31 04:00Z SFC–11,500 ft

  24NM E BAKER CITY, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7233 2026-07-21 14:00Z – 2026-08-04 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7244 2026-07-21 14:00Z – 2026-08-04 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7602 2026-07-22 14:00Z – 2026-08-05 05:00Z SFC–11,000 ft

  25NM NE JOHN DAY, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7603 2026-07-22 14:00Z – 2026-08-05 05:00Z SFC–11,000 ft

  25NM NE JOHN DAY, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 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