Diversion — FDX1685
KSEA · 16L2026-02-13 03:59 UTC· KTUS → KSEA· FEDERAL EXPRESS CORP· B763
FDX1685 (Federal Express) was operating from KTUS to KIND (Indianapolis International Airport) on 2026-02-13. SkyMeter detected a diversion to Seattle Tacoma International Airport (KSEA) on runway 16L at 03:59 UTC. Peak cruise altitude FL406, turnaround area near Eureka County, US. Approach stability score: 93/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 8 kt wind, 3 kt crosswind component, 193 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local
View FAA NOTAM → - SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 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 16L
- 347 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 93/100
- 8 kt wind
- 3 kt crosswind component
- 193 m visibility
- KSEA 081453Z 00000KT 1/8SM R16L/1000V1200FT FG VV001 11/11 A3010 RMK AO2 SLP200 T01110106 55001
Flight context
- FDX1685
- Federal Express
- B763
- KTUS → KSEA
- 2026-02-13 03:59 UTC
- KSEA runway 16L
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