Not currently tracked · last seen 3d ago
- Flights observed
- 40
- Avg flight time
- 35m
- Typical route
- -
- Last seen
- 3d ago
Last known area
Recent flights last 40
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | - | May 30, 19:50 UTC | May 30, 20:10 UTC | 20m |
| 2026-05-30 | - | May 30, 14:25 UTC | May 30, 14:45 UTC | 20m |
| 2026-05-22 | - | May 22, 23:20 UTC | May 23, 00:05 UTC | 45m |
| 2026-05-22 | - | May 22, 20:45 UTC | May 22, 22:15 UTC | 1h 30m |
| 2026-05-22 | - | May 22, 15:15 UTC | May 22, 17:20 UTC | 2h 5m |
| 2026-05-22 | - | May 22, 03:30 UTC | May 22, 03:45 UTC | 15m |
| 2026-05-22 | - | May 22, 02:15 UTC | May 22, 02:35 UTC | 20m |
| 2026-05-13 | - | May 13, 22:00 UTC | May 13, 22:35 UTC | 35m |
| 2026-05-13 | - | May 13, 15:05 UTC | May 13, 15:45 UTC | 40m |
| 2026-05-09 | - | May 9, 22:00 UTC | May 9, 22:39 UTC | 40m |
| 2026-05-09 | - | May 9, 20:44 UTC | May 9, 21:14 UTC | 30m |
| 2026-05-09 | - | May 9, 19:14 UTC | May 9, 19:40 UTC | 25m |
| 2026-05-09 | - | May 9, 14:35 UTC | May 9, 15:05 UTC | 30m |
| 2026-05-08 | - | May 8, 23:30 UTC | May 8, 23:40 UTC | 10m |
| 2026-05-08 | - | May 8, 21:40 UTC | May 8, 21:50 UTC | 10m |
| 2026-05-08 | - | May 8, 18:05 UTC | May 8, 18:45 UTC | 40m |
| 2026-05-08 | - | May 8, 13:10 UTC | May 8, 13:50 UTC | 40m |
| 2026-05-07 | - | May 7, 19:00 UTC | May 7, 20:15 UTC | 1h 15m |
| 2026-05-07 | - | May 7, 15:20 UTC | May 7, 16:45 UTC | 1h 25m |
| 2026-05-02 | - | May 2, 18:30 UTC | May 2, 18:50 UTC | 20m |
| 2026-05-02 | - | May 2, 15:35 UTC | May 2, 16:10 UTC | 35m |
| 2026-05-01 | - | May 1, 23:25 UTC | May 2, 00:35 UTC | 1h 10m |
| 2026-05-01 | - | May 1, 21:40 UTC | May 1, 21:55 UTC | 15m |
| 2026-04-30 | - | Apr 30, 20:20 UTC | Apr 30, 21:15 UTC | 55m |
| 2026-04-30 | - | Apr 30, 18:55 UTC | Apr 30, 19:05 UTC | 10m |
| 2026-04-30 | - | Apr 30, 18:30 UTC | Apr 30, 18:35 UTC | 5m |
| 2026-04-30 | - | Apr 30, 17:50 UTC | Apr 30, 18:20 UTC | 30m |
| 2026-04-24 | - | Apr 24, 21:20 UTC | Apr 24, 21:30 UTC | 10m |
| 2026-04-19 | - | Apr 19, 00:30 UTC | Apr 19, 00:55 UTC | 25m |
| 2026-04-18 | - | Apr 18, 23:35 UTC | Apr 18, 23:55 UTC | 20m |
| 2026-04-18 | - | Apr 18, 16:40 UTC | Apr 18, 16:55 UTC | 15m |
| 2026-04-18 | - | Apr 18, 01:25 UTC | Apr 18, 01:50 UTC | 25m |
| 2026-04-18 | - | Apr 18, 00:40 UTC | Apr 18, 01:20 UTC | 40m |
| 2026-04-18 | - | Apr 18, 00:00 UTC | Apr 18, 00:10 UTC | 10m |
| 2026-04-17 | - | Apr 17, 22:35 UTC | Apr 17, 23:10 UTC | 35m |
| 2026-04-17 | - | Apr 17, 21:40 UTC | Apr 17, 22:05 UTC | 25m |
| 2026-04-17 | - | Apr 17, 18:30 UTC | Apr 17, 18:50 UTC | 20m |
| 2026-04-17 | SJC → PAO | Apr 17, 17:50 UTC | Apr 17, 18:20 UTC | 30m |
| 2026-04-17 | - | Apr 17, 15:25 UTC | Apr 17, 15:35 UTC | 10m |
| 2026-04-17 | - | Apr 17, 13:40 UTC | Apr 17, 15:05 UTC | 1h 25m |
Specifications
| Registration | N719KF |
| Operator | VANNOY CORY |
| Mode-S code | A99E63 · 52317143 (octal) |
Looking for transponder-level data? View the Mode-S A99E63 page for country allocation, callsign history, and ADS-B signal details.
N719KF frequently asked
Who operates N719KF?
N719KF is operated by VANNOY CORY.
What is the Mode-S transponder code for N719KF?
N719KF broadcasts on Mode-S (ICAO 24-bit) address A99E63 (octal 52317143). View the transponder page.
Where is N719KF right now?
N719KF is not currently being tracked; last seen 3d ago.