sensors Mode-S transponder
C05213
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GFCC · LEARJET 45
- Hex
- C05213
- Octal
- 60051023
- Decimal
- 12,603,923
- Country
- CA
- Tail
- C-GFCC
- Type
- LJ45
- Flights observed
- 86
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C05213 falls within the block assigned to Canada (CA) by ICAO Annex 10, Volume III. Every aircraft registered in Canada receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| KNT999 | - | 86 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | KNT999 | - | Jul 13, 03:20 UTC | Jul 13, 06:10 UTC | 2h 50m |
| 2026-07-12 | KNT999 | - | Jul 12, 21:35 UTC | Jul 13, 01:10 UTC | 3h 35m |
| 2026-07-12 | KNT999 | - | Jul 12, 14:25 UTC | Jul 12, 16:15 UTC | 1h 50m |
| 2026-07-12 | KNT999 | - | Jul 12, 09:55 UTC | Jul 12, 10:50 UTC | 55m |
| 2026-07-12 | KNT999 | YUL → YQB | Jul 12, 08:01 UTC | Jul 12, 08:30 UTC | 30m |
| 2026-07-03 | KNT999 | BOS → YUL | Jul 3, 20:00 UTC | Jul 3, 20:45 UTC | 45m |
| 2026-07-02 | KNT999 | YUL → BOS | Jul 2, 14:00 UTC | Jul 2, 14:50 UTC | 50m |
| 2026-06-21 | KNT999 | - | Jun 21, 19:39 UTC | Jun 21, 21:14 UTC | 1h 35m |
| 2026-06-21 | KNT999 | - | Jun 21, 10:34 UTC | Jun 21, 11:55 UTC | 1h 20m |
| 2026-06-20 | KNT999 | - | Jun 20, 05:14 UTC | Jun 20, 12:19 UTC | 7h 5m |
| 2026-06-20 | KNT999 | - | Jun 20, 03:24 UTC | Jun 20, 04:24 UTC | 1h 0m |
| 2026-06-15 | KNT999 | - | Jun 15, 01:00 UTC | Jun 15, 03:15 UTC | 2h 15m |
| 2026-06-14 | KNT999 | - | Jun 14, 22:30 UTC | Jun 15, 00:20 UTC | 1h 50m |
| 2026-06-14 | KNT999 | - | Jun 14, 20:25 UTC | Jun 14, 21:15 UTC | 50m |
| 2026-06-14 | KNT999 | - | Jun 14, 00:10 UTC | Jun 14, 03:30 UTC | 3h 20m |
| 2026-06-13 | KNT999 | - | Jun 13, 20:30 UTC | Jun 13, 23:10 UTC | 2h 40m |
| 2026-06-13 | KNT999 | KEF → YUL | Jun 13, 13:25 UTC | Jun 13, 19:25 UTC | 6h 0m |
| 2026-06-13 | KNT999 | - | Jun 13, 10:35 UTC | Jun 13, 12:45 UTC | 2h 10m |
| 2026-06-12 | KNT999 | - | Jun 12, 09:15 UTC | Jun 12, 11:25 UTC | 2h 10m |
| 2026-06-12 | KNT999 | - | Jun 12, 02:25 UTC | Jun 12, 08:00 UTC | 5h 35m |
| 2026-06-10 | KNT999 | MSP → YUL | Jun 10, 03:00 UTC | Jun 10, 04:55 UTC | 1h 55m |
| 2026-06-09 | KNT999 | - | Jun 9, 21:55 UTC | Jun 10, 00:10 UTC | 2h 15m |
| 2026-06-09 | KNT999 | - | Jun 9, 14:50 UTC | Jun 9, 20:45 UTC | 5h 55m |
| 2026-06-09 | KNT999 | - | Jun 9, 10:30 UTC | Jun 9, 13:40 UTC | 3h 10m |
| 2026-06-08 | KNT999 | KEF → FRA | Jun 8, 08:55 UTC | Jun 8, 12:10 UTC | 3h 15m |
| 2026-06-08 | KNT999 | - | Jun 8, 07:20 UTC | Jun 8, 07:40 UTC | 20m |
| 2026-06-08 | KNT999 | - | Jun 8, 01:45 UTC | Jun 8, 02:35 UTC | 50m |
| 2026-06-04 | KNT999 | YYZ → YUL | Jun 4, 02:10 UTC | Jun 4, 03:00 UTC | 50m |
| 2026-06-03 | KNT999 | - | Jun 3, 21:50 UTC | Jun 3, 22:35 UTC | 45m |
| 2026-06-03 | KNT999 | - | Jun 3, 13:05 UTC | Jun 3, 21:00 UTC | 7h 55m |
| 2026-06-03 | KNT999 | - | Jun 3, 09:25 UTC | Jun 3, 12:20 UTC | 2h 55m |
| 2026-06-02 | KNT999 | - | Jun 2, 13:50 UTC | Jun 2, 15:10 UTC | 1h 20m |
| 2026-06-02 | KNT999 | - | Jun 2, 11:15 UTC | Jun 2, 12:45 UTC | 1h 30m |
| 2026-06-01 | KNT999 | YUL → CAT | Jun 1, 01:15 UTC | Jun 1, 11:20 UTC | 10h 5m |
| 2026-05-31 | KNT999 | - | May 31, 20:25 UTC | May 31, 23:40 UTC | 3h 15m |
| 2026-05-30 | KNT999 | - | May 30, 17:55 UTC | May 30, 18:05 UTC | 10m |
| 2026-05-30 | KNT999 | - | May 30, 14:05 UTC | May 30, 17:20 UTC | 3h 15m |
| 2026-05-19 | KNT999 | - | May 19, 14:30 UTC | May 19, 16:50 UTC | 2h 20m |
| 2026-05-18 | KNT999 | CUN → YUL | May 18, 20:25 UTC | May 19, 00:30 UTC | 4h 5m |
| 2026-05-18 | KNT999 | TPA → CUN | May 18, 17:30 UTC | May 18, 19:00 UTC | 1h 29m |
| 2026-05-18 | KNT999 | - | May 18, 13:45 UTC | May 18, 16:25 UTC | 2h 40m |
| 2026-05-14 | KNT999 | - | May 14, 22:45 UTC | May 14, 23:50 UTC | 1h 5m |
| 2026-05-14 | KNT999 | - | May 14, 17:10 UTC | May 14, 17:55 UTC | 45m |
| 2026-05-14 | KNT999 | - | May 14, 12:55 UTC | May 14, 13:35 UTC | 40m |
| 2026-05-12 | KNT999 | - | May 12, 02:50 UTC | May 12, 04:15 UTC | 1h 25m |
| 2026-05-11 | KNT999 | - | May 11, 19:20 UTC | May 11, 22:35 UTC | 3h 14m |
| 2026-05-11 | KNT999 | - | May 11, 07:10 UTC | May 11, 09:20 UTC | 2h 10m |
| 2026-05-10 | KNT999 | - | May 10, 21:30 UTC | May 11, 05:10 UTC | 7h 40m |
| 2026-05-10 | KNT999 | - | May 10, 17:34 UTC | May 10, 20:40 UTC | 3h 5m |
| 2026-05-10 | KNT999 | BCN → AMS | May 10, 12:44 UTC | May 10, 14:30 UTC | 1h 45m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the C-GFCC page for operator, model, and routing details .