Long landing rollout — EJA782
KJAC · 192026-07-13 18:22 UTC· KTEB → KJAC· NETJETS SALES INC, CHESAPEAKE ENERGY CORP, JANEWAY WILLIAM H, FW· CL35
EJA782 (Netjets Sales) was operating from KTEB to KJAC on 2026-07-13. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 19 at 18:22 UTC. Trace data at the event: 6397 ft AGL, 9 kt GS. METAR at the time reported 5 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)- SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft
Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/1781 2026-06-30 15:00Z – 2026-07-14 03:00Z SFC–8,000 ft
9NM NW CRAWFORD, NE, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2268 2026-07-01 13:00Z – 2026-07-14 03:00Z SFC–14,500 ft
27NM SE JACKSON, WY, Wednesday, July 1, 2026 through Tuesday, July 14, 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
- 9 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KJAC 180356Z AUTO 05004KT 10SM CLR 09/08 A3030 RMK AO2 SLP239 T00890083
Flight context
- EJA782
- Netjets Sales
- CL35
- KTEB → KJAC
- 2026-07-13 18:22 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