Diversion — FFT3941
KTPA · 19R2026-05-31 18:13 UTC· KISP → KTPA· BANK OF UTAH TRUSTEE· A320
FFT3941 (Bank of Utah) was operating from KISP to KMCO (Orlando International Airport) on 2026-05-31. SkyMeter detected a diversion to Tampa International Airport (KTPA) on runway 19R at 18:13 UTC. Peak cruise altitude FL396, turnaround area near Surf City, US. Approach stability score: 61/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 10 kt wind, 7 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft
Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 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 19R
- 11 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 61/100
- 10 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KTPA 200450Z AUTO 00000KT 10SM FEW022 SCT100 25/22 A2997 RMK T02500220 MADISHF
Flight context
- FFT3941
- Bank of Utah
- A320
- KISP → KTPA
- 2026-05-31 18:13 UTC
- KTPA runway 19R
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