Long landing rollout — UAL1537
KJAC · 192026-08-09 22:54 UTC· KDEN → KJAC· UNITED AIRLINES INC· A320
UAL1537 (United Airlines) was operating from KDEN to KJAC on 2026-08-09. SkyMeter detected a long landing rollout at Jackson Hole Airport (KJAC) on runway 19 at 22:54 UTC. Trace data at the event: 6420 ft AGL, 0 kt GS. METAR at the time reported 14 kt wind, 12 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/2488 2026-08-06 14:00Z – 2026-08-20 05:00Z SFC–13,500 ft
28NM W AFTON, WY, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2917 2026-08-08 14:00Z – 2026-08-22 05:00Z SFC–13,500 ft
20NM E AFTON, WY, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3139 2026-08-09 22:49Z – 2026-08-11 04:00Z SFC–16,000 ft
13NM SE LANDER, WY, Sunday, August 9, 2026 through Tuesday, August 11, 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
- 6420 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 14 kt wind
- 12 kt crosswind component
- 16,093 m visibility
- KJAC 170630Z AUTO 36005KT 10SM CLR 07/03 A3027 RMK T00700030 MADISHF
Flight context
- UAL1537
- United Airlines
- A320
- KDEN → KJAC
- 2026-08-09 22:54 UTC
- KJAC runway 19
All events on this flight
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