Long landing rollout — TIV906
KJAC · 192026-07-22 17:29 UTC· KTEB → KJAC· M6 CARSON LLC· GLF4
TIV906 (M6 Carson) was operating from KTEB to KJAC on 2026-07-22. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 19 at 17:29 UTC. Trace data at the event: 6400 ft AGL, 3 kt GS. Approach stability score: 92/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 3 kt wind, 3 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/5841 2026-07-16 13:00Z – 2026-07-27 05:59Z SFC–400 ft
Cheyenne, WY, Thursday, July 16, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/5564 2026-07-20 19:15Z – 2026-07-23 23:30Z SFC–16,000 ft
Oshkosh, WI, Monday, July 20, 2026 through Thursday, July 23, 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
- 6400 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- Approach stability 92/100
- 3 kt wind
- 3 kt crosswind component
- 6,437 m visibility
- KJAC 171756Z 19003KT 4SM RA BR FEW006 SCT043 OVC065 11/10 A3036 RMK AO2 LTG DSNT S-W SLP263 P0010 60035 T01060100 10111 20078 51008
Flight context
- TIV906
- M6 Carson
- GLF4
- KTEB → KJAC
- 2026-07-22 17:29 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