LYM3712 (CBG) was operating from KDEN to KTEX on 2026-08-27. SkyMeter detected a go-around at Telluride Regional Airport (KTEX) on runway 09 at 18:25 UTC. Trace data at the event: 10792 ft AGL, 203 kt GS. METAR at the time reported 5 kt wind, 2 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft
20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/7117 2026-08-23 11:00Z – 2026-08-29 01:00Z SFC–13,500 ft
30NM SW PUEBLO, CO, Sunday, August 23, 2026 through Saturday, August 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/7463 2026-08-25 12:00Z – 2026-09-08 08:00Z SFC–16,500 ft
1NM NE OURAY, CO, Tuesday, August 25, 2026 through Tuesday, September 8, 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 09
- 10792 ft AGL at event
- 203 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KTEX 070515Z AUTO 00000KT 10SM OVC100 14/06 A3041 RMK AO2
Flight context
- LYM3712
- CBG
- J328
- KDEN → KTEX
- 2026-08-27 18:25 UTC
- KTEX runway 09
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