Go-around — FFT2953
KTPA · 01L2026-08-29 21:39 UTC· KIAD → KTPA· BANK OF UTAH TRUSTEE· A20N
FFT2953 (Bank of Utah) was operating from KIAD to KTPA on 2026-08-29. SkyMeter detected a go-around at Tampa International Airport (KTPA) on runway 01L at 21:39 UTC. Trace data at the event: 300 ft AGL, 159 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 3 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/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft
Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local
View FAA NOTAM → - VIP6/8638 2026-08-28 20:00Z – 2026-08-30 21:00Z SFC–4,999 ft
Middleburg, VA, Friday, August 28, 2026 through Sunday, August 30, 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 01L
- 300 ft AGL at event
- 159 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KTPA 162053Z 04010G20KT 10SM SCT046 BKN250 32/21 A3011 RMK AO2 SLP194 T03220206 55017
Flight context
- FFT2953
- Bank of Utah
- A20N
- KIAD → KTPA
- 2026-08-29 21:39 UTC
- KTPA runway 01L
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