Flight Status & Tracker

N321JZ

PASAN KAHANDAWA · TYS → KTTA · Last tracked Oct 17, 2026

N321JZ is a flight number operated by PASAN KAHANDAWA between McGhee Tyson Airport (KTYS) and Sanford-Lee County Regional Airport (KTTA). SkyMeter last tracked N321JZ on October 16, 2026. The flight is most often flown by a CIRRUS Cirrus SR-22 Turbo. Typical block time is 1h 23m. SkyMeter has observed 39 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
39
last 90 days
⏱
AVG DURATION
1h 23m
tracked time
📅
SERVICE PERIOD
5/22/2026 → 10/17/2026
first → last seen
🗺
ROUTES / TYPES
27 / 1
city pairs · airframes
⚠
INCIDENT RATE
10.3%
4 flagged

Routes flown

By count · last 90 days

10
KTYS → KTTA
4
avg 1h 23m · McGhee Tyson → Sanford-Lee County
KTTA → KSOP
2
avg 2h 24m · Sanford-Lee County → Moore County
KJZI → KTTA
2
avg 1h 5m · Charleston Executive → Sanford-Lee County
KTTA → KTYS
2
avg 1h 34m · Sanford-Lee County → McGhee Tyson
KRKW → KTYS
1
avg 46m · Rockwood → McGhee Tyson
KSHV → KE13
1
avg 2h 46m · Shreveport → Crane County
KTYS → KISM
1
avg 2h 50m · McGhee Tyson → Kissimmee Gateway
KTTA → KEQY
1
avg 35m · Sanford-Lee County → Charlotte-Monroe Executive
KTYS → KSHV
1
avg 3h 1m · McGhee Tyson → Shreveport
SC65 → KJZI
1
avg 7m · Raven's Run → Charleston Executive

Aircraft types

Equipment used on this number

1
S22T CIRRUS Cirrus SR-22 Turbo
45

Safety profile

Flagged flights · last 90 days

Go-arounds
0
Unstable approach
4
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 N321JZ

30
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/17/2026
16m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/16/2026
2h 35m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/16/2026
7m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/15/2026
6h 59m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/15/2026
1h 53m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/15/2026
2h 45m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/15/2026
3h 0m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/14/2026
1h 29m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/14/2026
46m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/14/2026
37m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/13/2026
35m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/8/2026
1h 25m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/8/2026
1h 18m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
10/8/2026
37m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/25/2026
2h 49m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/24/2026
4m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/24/2026
1h 35m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/20/2026
2h 6m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/18/2026
2h 20m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/12/2026
1h 3m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/10/2026
7m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/10/2026
38m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/10/2026
3h 3m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/10/2026
49m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/10/2026
9m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/9/2026
1h 9m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/9/2026
1h 7m
△ Low approach-stability score
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
9/1/2026
1h 30m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
8/26/2026
1h 27m
No alerts
Replay Analysis
N321JZCIRRUS Cirrus SR-22 Turbo
→
8/25/2026
33m
No alerts
Replay Analysis
© SkyMeter · All flight data subject to ODbL attribution · Tracked: 90-day window