Long landing rollout — N22VK
KJAC · 192026-07-30 20:51 UTC· KHND → KJAC· PREMIER 1ABMP LLC· PRM1
N22VK (Premier 1abmp) was operating from KHND to KJAC on 2026-07-30. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 19 at 20:51 UTC. Trace data at the event: 6397 ft AGL, 8 kt GS. METAR at the time reported 8 kt wind, 4 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/6567 2026-07-18 13:00Z – 2026-08-01 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Saturday, July 18, 2026 through Saturday, August 1, 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/6736 2026-07-19 12:00Z – 2026-08-01 03:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Sunday, July 19, 2026 through Saturday, August 1, 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/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/7220 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–12,000 ft
19NM SW MEEKER, 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/8008 2026-07-23 12:00Z – 2026-08-01 03:00Z SFC–12,000 ft
16NM W MONTICELLO, UT, Thursday, July 23, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/8012 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft
16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/9861 2026-07-29 00:45Z – 2026-08-01 04:00Z SFC–12,500 ft
19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/9884 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–12,500 ft
19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9802 2026-07-29 12:00Z – 2026-08-11 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/9875 2026-07-29 12:00Z – 2026-08-03 04:00Z SFC–11,500 ft
20NM W RICHFIELD, UT, Wednesday, July 29, 2026 through Monday, August 3, 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.
Pilot review data
- Runway 19
- 6397 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KJAC 171156Z AUTO 21006KT 10SM VCTS -RA FEW060 BKN095 OVC120 10/05 A3031 RMK AO2 TSB54RAB54 SLP211 P0000 60000 T01000050 10100 20061 53008
Flight context
- N22VK
- Premier 1abmp
- PRM1
- KHND → KJAC
- 2026-07-30 20:51 UTC
- KJAC runway 19
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