Diversion — UAL1717
KCOS · 17L2026-08-22 21:52 UTC· KJAC → KCOS· UNITED AIRLINES INC· A320
UAL1717 (United Airlines) was operating from KJAC to KDEN (Denver International Airport) on 2026-08-22. SkyMeter detected a diversion to City of Colorado Springs Municipal Airport (KCOS) on runway 17L at 21:52 UTC. Peak cruise altitude FL310, turnaround area near Saratoga, US. Approach stability score: 90/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/3161 2026-08-10 12:00Z – 2026-08-25 03:30Z SFC–16,000 ft
13NM SE LANDER, WY, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/4089 2026-08-12 12:00Z – 2026-08-27 03:30Z SFC–15,000 ft
2NM SE LANDER, WY, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft
8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 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 17L
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 90/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KCOS 161054Z 09004KT 10SM BKN190 11/07 A3028 RMK AO2 SLP196 T01110072 $
Flight context
- UAL1717
- United Airlines
- A320
- KJAC → KCOS
- 2026-08-22 21:52 UTC
- KCOS runway 17L
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