Go-around — FFT1783
KDEN · 16R2026-06-07 18:03 UTC· KBNA → KDEN· BANK OF UTAH TRUSTEE· A21N
FFT1783 (Bank of Utah) was operating from KBNA to KDEN on 2026-06-07. SkyMeter detected a go-around at Denver International Airport (KDEN) on runway 16R at 18:03 UTC. Trace data at the event: 6005 ft AGL, 162 kt GS. METAR at the time reported 3 kt wind, 1 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)- SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z
STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z
TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4146 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4149 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4154 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4155 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4157 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
PRAIRIE VILLAGE, KS, 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 → - SECURITY6/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4206 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, 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 16R
- 6005 ft AGL at event
- 162 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KDEN 181453Z 21008KT 10SM FEW100 SCT150 BKN200 21/12 A3021 RMK AO2 SLP158 T02060117 53001
Flight context
- FFT1783
- Bank of Utah
- A21N
- KBNA → KDEN
- 2026-06-07 18:03 UTC
- KDEN runway 16R
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