Long landing rollout — LXJ373

LXJ373 (Flexjet) was operating from KSNA to KJAC on 2026-07-23. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 01 at 01:39 UTC. Trace data at the event: 6400 ft AGL, 0 kt GS. METAR at the time reported 8 kt wind, 8 kt crosswind component, 6,437 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/4555 2026-07-10 14:00Z – 2026-07-23 04:00Z SFC–10,500 ft

  44NM NE WELLS, NV, Friday, July 10, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4895 2026-07-10 23:19Z – 2026-07-24 23:00Z SFC–10,500 ft

  3NM W PIÑON HILLS, CA, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4906 2026-07-11 02:45Z – 2026-07-24 04:00Z SFC–14,000 ft

  7NM N OREM, UT, Saturday, July 11, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4907 2026-07-11 15:00Z – 2026-07-24 23:00Z SFC–10,500 ft

  3NM W PIÑON HILLS, CA, Saturday, July 11, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4975 2026-07-12 13:00Z – 2026-07-26 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5145 2026-07-13 00:57Z – 2026-07-26 07:45Z SFC–8,500 ft

  3NM W PIÑON HILLS, CA, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5155 2026-07-13 13:00Z – 2026-07-26 04:00Z SFC–11,000 ft

  40NM NE WELLS, NV, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5274 2026-07-13 17:54Z – 2026-07-27 04:00Z SFC–15,500 ft

  15NM E HEBER CITY, UT, Monday, July 13, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6221 2026-07-16 17:58Z – 2026-07-30 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6358 2026-07-17 13:00Z – 2026-07-31 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6359 2026-07-17 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6569 2026-07-18 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6766 2026-07-19 17:32Z – 2026-07-26 04:00Z SFC–13,000 ft

  5NM N HAILEY, ID, Sunday, July 19, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6858 2026-07-20 14:00Z – 2026-08-04 04:00Z SFC–13,000 ft

  5NM N HAILEY, ID, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 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/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft

  20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 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