Return to field — N102WY
KCYS2026-08-05 17:34 UTC· KCYS → KCYS· WYOMING DEPARTMENT OF TRANSPORTATION, AERONAUTICS DIVISION· C560
N102WY (Wyoming Department of Transportation) had departed KCYS on 2026-08-05. SkyMeter detected a return to field at Cheyenne Regional Jerry Olson Field (KCYS) at 17:34 UTC. Peak cruise altitude FL381, turnaround area near Steamboat Springs, US. Approach stability score: 38/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/9884 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–12,500 ft
19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/2269 2026-08-05 18:53Z – 2026-08-07 03:00Z SFC–13,500 ft
19NM E STEAMBOAT SPRINGS, CO, Wednesday, August 5, 2026 through Friday, August 7, 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
- 38167 ft AGL at event
- 434 kt ground speed
- 0 fpm vertical
- Approach stability 38/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KCYS 162153Z AUTO 26012G18KT 10SM CLR 23/08 A3029 RMK AO2 RAE09 SLP183 P0000 T02330078
Flight context
- N102WY
- Wyoming Department of Transportation
- C560
- KCYS → KCYS
- 2026-08-05 17:34 UTC
- KCYS
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