Flight Status & Tracker

N412CP

JOHNSON JOHN C III · KJYO → CHO · Last tracked Nov 5, 2026

N412CP is a flight number operated by JOHNSON JOHN C III between Leesburg Executive Airport (KJYO) and Charlottesville Albemarle Airport (KCHO). SkyMeter last tracked N412CP on November 5, 2026. The flight is most often flown by a CIRRUS Cirrus SR 22. Typical block time is 1h 13m. SkyMeter has observed 37 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
37
last 90 days
⏱
AVG DURATION
1h 13m
tracked time
📅
SERVICE PERIOD
5/27/2025 → 11/5/2026
first → last seen
🗺
ROUTES / TYPES
26 / 1
city pairs · airframes
⚠
INCIDENT RATE
10.8%
4 flagged

Routes flown

By count · last 90 days

10
KJYO → KCHO
3
avg 31m · Leesburg Executive → Charlottesville Albemarle
KCHO → KBCB
2
avg 1h 26m · Charlottesville Albemarle → Virginia Tech Montgomery Executive
KJYO → KART
2
avg 1h 58m · Leesburg Executive → Watertown
KART → KJYO
2
avg 2h 24m · Watertown → Leesburg Executive
KBCB → KCHO
2
avg 52m · Virginia Tech Montgomery Executive → Charlottesville Albemarle
KPMP → F57
1
avg 1h 20m · Pompano Beach Airpark → Jack Browns Seaplane Base
KDMW → KJYO
1
avg 44m · Carroll County Regional Jack B Poage Field → Leesburg Executive
KGIF → KOGB
1
avg 2h 19m · Winter Haven Regional Airport - Gilbert Field → Orangeburg
KOKV → KJYO
1
avg 13m · Winchester → Leesburg Executive
KOGB → KLEE
1
avg 1h 47m · Orangeburg → Leesburg

Aircraft types

Equipment used on this number

1
SR22 CIRRUS Cirrus SR 22
41

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 N412CP

30
N412CPCIRRUS Cirrus SR 22
→
11/5/2026
2h 26m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
11/5/2026
2h 6m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
11/4/2026
2h 21m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
11/4/2026
1h 49m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/26/2026
35m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/26/2026
23m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/25/2026
2h 1m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/25/2026
1h 38m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/25/2026
2h 19m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/25/2026
1h 20m
△ Low approach-stability score
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/24/2026
1h 6m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/24/2026
21m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/24/2026
19m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/24/2026
1h 27m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/24/2026
1h 46m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/23/2026
1h 56m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/23/2026
29m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/23/2026
1h 45m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/9/2026
1h 23m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/8/2026
13m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/8/2026
15m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/6/2026
13m
△ Low approach-stability score
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/6/2026
41m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/6/2026
17m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/6/2026
54m
△ Low approach-stability score
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/5/2026
1h 33m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
10/5/2026
29m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
9/26/2026
48m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
9/26/2026
8m
No alerts
Replay Analysis
N412CPCIRRUS Cirrus SR 22
→
9/26/2026
2h 48m
No alerts
Replay Analysis
© SkyMeter · All flight data subject to ODbL attribution · Tracked: 90-day window