Return to field — TKR169
KCOS · 17L2026-07-06 18:29 UTC· KCOS → KCOS· BANK OF UTAH TRUSTEE· RJ85
TKR169 (Bank of Utah) had departed KCOS on 2026-07-06. SkyMeter detected a return to field at City of Colorado Springs Municipal Airport (KCOS) on runway 17L at 18:29 UTC. Peak altitude 17,128 ft, turnaround area near Florence, US. Approach stability score: 34/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). 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/1416 2026-06-29 14:37Z – 2026-07-14 04:00Z SFC–13,500 ft
15NM NW CAÑON CITY, CO, Monday, June 29, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 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
- 17128 ft AGL at event
- 341 kt ground speed
- 0 fpm vertical
- Approach stability 34/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KCOS 161954Z 14003KT 10SM FEW085 SCT140 BKN200 24/08 A3029 RMK AO2 SLP185 T02440083 $
Flight context
- TKR169
- Bank of Utah
- RJ85
- KCOS → KCOS
- 2026-07-06 18:29 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