Go-around — JSX661
KAPA · 17L2026-07-16 22:02 UTC· KLAS → KAPA· DELUX PUBLIC CHARTER LLC· E145
JSX661 (Delux Public Charter) was operating from KLAS to KAPA on 2026-07-16. SkyMeter detected a go-around at Centennial Airport (KAPA) on runway 17L at 22:02 UTC. Trace data at the event: 6803 ft AGL, 179 kt GS. METAR at the time reported 13 kt wind, 8 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/2812 2026-07-03 02:53Z – 2026-07-17 04:00Z SFC–17,000 ft
1NM N OURAY, CO, Friday, July 3, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/2845 2026-07-04 00:10Z – 2026-07-17 04:00Z SFC–12,500 ft
6NM S SCIPIO, UT, Saturday, July 4, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/2942 2026-07-05 12:00Z – 2026-07-19 04:00Z SFC–17,000 ft
2NM W LEADVILLE, CO, Sunday, July 5, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/3006 2026-07-06 12:00Z – 2026-07-20 04:00Z SFC–12,000 ft
15NM W GRAND JUNCTION, CO, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3007 2026-07-06 12:00Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3021 2026-07-06 14:00Z – 2026-07-19 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Monday, July 6, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/3274 2026-07-07 00:35Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Tuesday, July 7, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3372 2026-07-07 02:34Z – 2026-07-20 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Tuesday, July 7, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft
1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/3812 2026-07-08 02:09Z – 2026-07-21 04:00Z SFC–12,000 ft
6NM S SCIPIO, UT, Wednesday, July 8, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/4199 2026-07-09 02:00Z – 2026-07-23 05:00Z SFC–13,000 ft
18NM N CORTEZ, CO, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/4554 2026-07-10 02:28Z – 2026-07-17 04:00Z SFC–15,500 ft
8NM E BEAVER, UT, Friday, July 10, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/4561 2026-07-10 04:00Z – 2026-07-24 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4562 2026-07-10 12:00Z – 2026-07-24 05:00Z SFC–17,000 ft
3NM W LEADVILLE, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/5450 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/5451 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 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
- 6803 ft AGL at event
- 179 kt ground speed
- 0 fpm vertical
- 13 kt wind
- 8 kt crosswind component
- 16,093 m visibility
- KAPA 161853Z VRB04KT 10SM FEW110 SCT140 BKN220 27/09 A3026 RMK AO2 SLP176 T02670089
Flight context
- JSX661
- Delux Public Charter
- E145
- KLAS → KAPA
- 2026-07-16 22:02 UTC
- KAPA runway 17L
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