Not currently tracked · last seen 6h ago
- Flights observed
- 143 showing last 50
- Avg flight time
- 1h 6m
- Typical route
- BJC → BJC
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | BJC → BJC | Jul 14, 02:45 UTC | Jul 14, 03:30 UTC | 45m |
| 2026-07-13 | BJC → BJC | Jul 13, 20:55 UTC | Jul 13, 21:45 UTC | 50m |
| 2026-07-13 | BJC → BJC | Jul 13, 17:45 UTC | Jul 13, 19:25 UTC | 1h 40m |
| 2026-07-13 | BJC → BJC | Jul 13, 14:45 UTC | Jul 13, 15:40 UTC | 55m |
| 2026-07-13 | BJC → BJC | Jul 13, 12:55 UTC | Jul 13, 13:55 UTC | 1h 0m |
| 2026-07-12 | BJC → BJC | Jul 12, 20:01 UTC | Jul 12, 20:45 UTC | 45m |
| 2026-07-12 | BJC → BJC | Jul 12, 16:05 UTC | Jul 12, 17:50 UTC | 1h 45m |
| 2026-07-12 | BJC → BJC | Jul 12, 12:55 UTC | Jul 12, 14:40 UTC | 1h 45m |
| 2026-07-12 | BJC → BJC | Jul 12, 01:50 UTC | Jul 12, 02:20 UTC | 30m |
| 2026-07-11 | BJC → BJC | Jul 11, 18:00 UTC | Jul 11, 19:40 UTC | 1h 40m |
| 2026-07-02 | BJC → BJC | Jul 2, 23:20 UTC | Jul 3, 00:45 UTC | 1h 25m |
| 2026-07-02 | BJC → BJC | Jul 2, 17:40 UTC | Jul 2, 18:30 UTC | 50m |
| 2026-07-02 | - | Jul 2, 15:40 UTC | Jul 2, 16:20 UTC | 40m |
| 2026-07-02 | BJC → BJC | Jul 2, 13:40 UTC | Jul 2, 14:55 UTC | 1h 15m |
| 2026-07-01 | BJC → BJC | Jul 1, 17:25 UTC | Jul 1, 18:25 UTC | 1h 0m |
| 2026-07-01 | BJC → BJC | Jul 1, 14:20 UTC | Jul 1, 15:20 UTC | 1h 0m |
| 2026-06-30 | BJC → BJC | Jun 30, 11:05 UTC | Jun 30, 12:45 UTC | 1h 40m |
| 2026-06-30 | BJC → BJC | Jun 30, 00:09 UTC | Jun 30, 01:40 UTC | 1h 31m |
| 2026-06-29 | BJC → BJC | Jun 29, 21:34 UTC | Jun 29, 22:19 UTC | 45m |
| 2026-06-29 | - | Jun 29, 19:35 UTC | Jun 29, 19:49 UTC | 15m |
| 2026-06-29 | - | Jun 29, 18:14 UTC | Jun 29, 19:29 UTC | 1h 15m |
| 2026-06-29 | BJC → BJC | Jun 29, 15:30 UTC | Jun 29, 16:50 UTC | 1h 20m |
| 2026-06-29 | BJC → BJC | Jun 29, 12:29 UTC | Jun 29, 14:04 UTC | 1h 35m |
| 2026-06-28 | BJC → BJC | Jun 28, 19:40 UTC | Jun 28, 22:04 UTC | 2h 25m |
| 2026-06-28 | BJC → BJC | Jun 28, 17:00 UTC | Jun 28, 17:39 UTC | 40m |
| 2026-06-28 | BJC → BJC | Jun 28, 13:59 UTC | Jun 28, 15:34 UTC | 1h 35m |
| 2026-06-24 | - | Jun 24, 19:39 UTC | Jun 24, 20:30 UTC | 50m |
| 2026-06-24 | - | Jun 24, 17:05 UTC | Jun 24, 17:14 UTC | 10m |
| 2026-06-23 | - | Jun 23, 20:04 UTC | Jun 23, 21:29 UTC | 1h 25m |
| 2026-06-23 | - | Jun 23, 01:54 UTC | Jun 23, 02:09 UTC | 15m |
| 2026-06-23 | BJC → LAR | Jun 23, 00:00 UTC | Jun 23, 00:54 UTC | 55m |
| 2026-06-22 | BJC → BJC | Jun 22, 16:50 UTC | Jun 22, 18:00 UTC | 1h 10m |
| 2026-06-22 | BJC → BJC | Jun 22, 13:59 UTC | Jun 22, 15:14 UTC | 1h 15m |
| 2026-06-19 | - | Jun 19, 12:34 UTC | Jun 19, 14:44 UTC | 2h 10m |
| 2026-06-15 | - | Jun 15, 12:45 UTC | Jun 15, 13:34 UTC | 50m |
| 2026-06-14 | BJC → BJC | Jun 14, 16:05 UTC | Jun 14, 17:20 UTC | 1h 15m |
| 2026-06-13 | - | Jun 13, 03:40 UTC | Jun 13, 04:20 UTC | 40m |
| 2026-06-12 | - | Jun 12, 23:20 UTC | Jun 13, 00:20 UTC | 1h 0m |
| 2026-06-12 | BJC → BJC | Jun 12, 20:05 UTC | Jun 12, 21:05 UTC | 1h 0m |
| 2026-06-12 | BJC → BJC | Jun 12, 17:05 UTC | Jun 12, 19:00 UTC | 1h 55m |
| 2026-06-12 | BJC → BJC | Jun 12, 14:50 UTC | Jun 12, 15:55 UTC | 1h 5m |
| 2026-06-11 | - | Jun 11, 20:05 UTC | Jun 11, 20:55 UTC | 50m |
| 2026-06-11 | - | Jun 11, 18:30 UTC | Jun 11, 19:30 UTC | 1h 0m |
| 2026-06-11 | BJC → BJC | Jun 11, 15:20 UTC | Jun 11, 16:35 UTC | 1h 15m |
| 2026-06-11 | BJC → BJC | Jun 11, 12:10 UTC | Jun 11, 12:20 UTC | 10m |
| 2026-06-10 | BJC → BJC | Jun 10, 16:30 UTC | Jun 10, 17:30 UTC | 1h 0m |
| 2026-06-10 | BJC → BJC | Jun 10, 13:20 UTC | Jun 10, 14:45 UTC | 1h 25m |
| 2026-06-09 | BJC → BJC | Jun 9, 14:55 UTC | Jun 9, 15:50 UTC | 55m |
| 2026-06-09 | BJC → BJC | Jun 9, 01:30 UTC | Jun 9, 02:25 UTC | 55m |
| 2026-06-08 | BJC → BJC | Jun 8, 18:45 UTC | Jun 8, 19:25 UTC | 40m |
Specifications
| Registration | N810KK |
| Operator | KENZY 2023 LLC |
| Mode-S code | AB0A47 · 52605107 (octal) |
Looking for transponder-level data? View the Mode-S AB0A47 page for country allocation, callsign history, and ADS-B signal details.
N810KK frequently asked
Who operates N810KK?
N810KK is operated by KENZY 2023 LLC.
What is the Mode-S transponder code for N810KK?
N810KK broadcasts on Mode-S (ICAO 24-bit) address AB0A47 (octal 52605107). View the transponder page.
What route does N810KK typically fly?
N810KK most frequently flies between BJC and BJC based on observed flights.
Where is N810KK right now?
N810KK is not currently being tracked; last seen 6h ago.