Return to field — TKR168
KCOS · 17L2026-07-06 19:55 UTC· KCOS → KCOS· AERO-FLITE INC· RJ85
TKR168 (Aero-Flite) 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 19:55 UTC. Peak altitude 9,505 ft, turnaround area near Penrose, US. Approach stability score: 40/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/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
- 9505 ft AGL at event
- 307 kt ground speed
- 0 fpm vertical
- Approach stability 40/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KCOS 152054Z 30015KT 10SM FEW065 SCT080 SCT120 BKN170 BKN230 26/11 A3033 RMK AO2 PK WND 30026/2042 WSHFT 2026 TSE02B04E40 SLP184 VIRGA N AND W CB DSNT N MOV NE AND W STRNY 60000 T02610111 55004 $
Flight context
- TKR168
- Aero-Flite
- RJ85
- KCOS → KCOS
- 2026-07-06 19:55 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