Go-around — N86CW
KCPS · 12R2026-07-01 12:50 UTC· KIAD → KCPS· COSTCO WHOLESALE CORP· G280
N86CW (Costco Wholesale) was operating from KIAD to KCPS on 2026-07-01. SkyMeter detected a go-around at St Louis Downtown Airport (KCPS) on runway 12R at 12:50 UTC. Trace data at the event: 788 ft AGL, 166 kt GS. METAR at the time reported 3 kt wind, 3 kt crosswind component, 12,875 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)- SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
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 12R
- 788 ft AGL at event
- 166 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 12,875 m visibility
- METAR KCPS 170253Z AUTO 14003KT 8SM CLR 24/23 A3023 RMK AO2 SLP232 T02390233 53012 $
Flight context
- N86CW
- Costco Wholesale
- G280
- KIAD → KCPS
- 2026-07-01 12:50 UTC
- KCPS runway 12R
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