Diversion — FFT1234
9NC0 · 012026-07-22 21:16 UTC· KMCO → 9NC0· WELLS FARGO TRUST CO NA TRUSTEE· A20N
FFT1234 (Wells Fargo Trust Co NA) was operating from KMCO to KRDU (Raleigh Durham International Airport) on 2026-07-22. SkyMeter detected a diversion to Raleigh East Airport (9NC0) on runway 01 at 21:16 UTC. Peak cruise altitude FL353, turnaround area near Kiawah Island, US. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 5 kt wind, 4 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - SECURITY6/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/6690 2026-07-22 21:05Z – 2026-07-23 01:47Z SFC–180 ft
Cape Canaveral, FL, Wednesday, July 22, 2026 through Wednesday, July 22, 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 01
- 313 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 40/100
- 5 kt wind
- 4 kt crosswind component
Flight context
- FFT1234
- Wells Fargo Trust Co NA
- A20N
- KMCO → 9NC0
- 2026-07-22 21:16 UTC
- 9NC0 runway 01
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