Go-around — FFT2898
KDTW · 21L2026-07-02 16:25 UTC· KATL → KDTW· UMB BANK NA TRUSTEE· A320
FFT2898 (UMB Bank NA) was operating from KATL to KDTW on 2026-07-02. SkyMeter detected a go-around at Detroit Metropolitan Wayne County Airport (KDTW) on runway 21L at 16:25 UTC. Trace data at the event: 2196 ft AGL, 183 kt GS. METAR at the time reported 11 kt wind, 14,484 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/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/0131 2026-06-30 11:00Z – 2026-07-07 02:00Z SFC–400 ft
Columbus, OH, Tuesday, June 30, 2026 through Tuesday, July 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
- Runway 21L
- 2196 ft AGL at event
- 183 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 0 kt crosswind component
- 14,484 m visibility
- KDTW 170353Z 03005KT 9SM -RA FEW009 BKN026 OVC046 18/15 A3031 RMK AO2 RAB0259E19B35 SLP262 P0000 T01830150
Flight context
- FFT2898
- UMB Bank NA
- A320
- KATL → KDTW
- 2026-07-02 16:25 UTC
- KDTW runway 21L
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