Flight Status & Tracker

N776SF

N · FCM → TYS · Last tracked Oct 24, 2026

N776SF is a flight number operated by between Flying Cloud Airport (KFCM) and McGhee Tyson Airport (KTYS). SkyMeter last tracked N776SF on October 24, 2026. The flight is most often flown by a CIRRUS Cirrus Vision SF50. Typical block time is 1h 19m. SkyMeter has observed 63 legs of this flight number via ADS-B.

SkyMeter tracks historical flight activity from ADS-B data — this is not a live gate-to-gate status feed.

✈
FLIGHTS
63
last 90 days
⏱
AVG DURATION
1h 19m
tracked time
📅
SERVICE PERIOD
5/20/2026 → 10/24/2026
first → last seen
🗺
ROUTES / TYPES
47 / 1
city pairs · airframes
⚠
INCIDENT RATE
7.9%
5 flagged

Routes flown

By count · last 90 days

10
KFCM → KTYS
2
avg 2h 35m · Flying Cloud → McGhee Tyson
KUES → KILN
2
avg 1h 13m · Waukesha County → Wilmington Airpark
KILN → KUES
2
avg 1h 28m · Wilmington Airpark → Waukesha County
KJWN → KTYS
2
avg 44m · John C Tune → McGhee Tyson
KMKT → KFCM
1
avg 16m · Mankato → Flying Cloud
KMSP → KFCM
1
avg 17m · Minneapolis-St Paul International/Wold-Chamberlain → Flying Cloud
KDAN → KFCM
1
avg 3h 14m · Danville → Flying Cloud
KCID → KFCM
1
avg 2h 25m · The Eastern Iowa → Flying Cloud
KFCM → KBRD
1
avg 37m · Flying Cloud → Brainerd Lakes
KUES → KAPA
1
avg 3h 8m · Waukesha County → Centennial

Aircraft types

Equipment used on this number

1
SF50 CIRRUS Cirrus Vision SF50
76

Safety profile

Flagged flights · last 90 days

Go-arounds
0
Unstable approach
5
Rejected TO
0
Stall warnings
0
Overspeeds
0
Runway excursion
0
Counts represent flights with at least one occurrence of each flag, not the total event count. See /incidents for individual events.

Recent flights

Newest 30 operations of N776SF

30
N776SFCIRRUS Cirrus Vision SF50
→
10/24/2026
1h 25m
△ Low approach-stability score
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/24/2026
1h 15m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/23/2026
1h 30m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/22/2026
1h 11m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/22/2026
1h 48m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/22/2026
1h 30m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/19/2026
2h 46m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/18/2026
3h 8m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/17/2026
37m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/16/2026
45m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/12/2026
1h 59m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
10/7/2026
23m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/24/2026
44m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/20/2026
56m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/19/2026
12m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/19/2026
37m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/19/2026
50m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/17/2026
2h 32m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/14/2026
42m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/12/2026
2h 24m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/12/2026
50m
△ Low approach-stability score
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/10/2026
2h 47m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/10/2026
36m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/9/2026
1h 30m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/9/2026
4h 33m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/9/2026
1h 13m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/9/2026
1h 38m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/9/2026
2h 52m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/8/2026
2h 44m
No alerts
Replay Analysis
N776SFCIRRUS Cirrus Vision SF50
→
9/6/2026
15m
No alerts
Replay Analysis
© SkyMeter · All flight data subject to ODbL attribution · Tracked: 90-day window