EmergencyDescent — FFT1233
2026-07-15 06:28 UTC· KRDU → ?· BANK OF UTAH TRUSTEE· A20N
FFT1233 (Bank of Utah) had departed KRDU on 2026-07-15. SkyMeter detected a emergencydescent at 06:28 UTC. Trace data at the event: 35258 ft AGL, 476 kt GS. METAR at the time reported 12 kt wind, 12 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC
View FAA NOTAM → - SECURITY6/5638 2026-07-15 02:00Z – 2026-07-15 06:00Z SFC–2,500 ft
MAYPORT, FL, Tuesday, July 14, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/5189 2026-07-15 06:43Z – 2026-07-15 11:35Z SFC–180 ft
Cape Canaveral, FL, Wednesday, July 15, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/5192 2026-07-15 06:43Z – 2026-07-15 11:35Z SFC–180 ft
Cape Canaveral, FL, Wednesday, July 15, 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
- 35258 ft AGL at event
- 476 kt ground speed
- 0 fpm vertical
- 12 kt wind
- 12 kt crosswind component
Flight context
- FFT1233
- Bank of Utah
- A20N
- 2026-07-15 06:28 UTC
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