Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

C01BC8

ICAO 24-bit transponder address · allocated to Canada

Currently assigned to C-FKNN · BOMBARDIER CL-600 Challenger · operated by FLYGTA Inc.

Hex
C01BC8
Octal
60015710
Decimal
12,590,024
Country
CA
Tail
C-FKNN
Type
CL60
No current signal · last broadcast 4h ago
Flights observed
79
Distinct callsigns
1
Country
CA
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S C01BC8.

Country allocation

The ICAO 24-bit address C01BC8 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
TOR800 - 79 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TOR800 - Jul 14, 14:10 UTCJul 14, 18:40 UTC4h 30m
2026-07-13 TOR800 - Jul 13, 16:50 UTCJul 13, 17:20 UTC30m
2026-07-13 TOR800 - Jul 13, 14:45 UTCJul 13, 16:10 UTC1h 25m
2026-07-12 TOR800 - Jul 12, 07:45 UTCJul 12, 09:45 UTC2h 0m
2026-07-12 TOR800 - Jul 12, 00:10 UTCJul 12, 06:35 UTC6h 25m
2026-07-11 TOR800 - Jul 11, 19:15 UTCJul 11, 23:15 UTC4h 0m
2026-07-10 TOR800 - Jul 10, 22:20 UTCJul 11, 00:10 UTC1h 50m
2026-07-10 TOR800 - Jul 10, 18:50 UTCJul 10, 21:15 UTC2h 25m
2026-07-10 TOR800 YYZ → APA Jul 10, 14:45 UTCJul 10, 18:05 UTC3h 20m
2026-07-08 TOR800 - Jul 8, 23:00 UTCJul 8, 23:25 UTC25m
2026-07-08 TOR800 - Jul 8, 20:10 UTCJul 8, 22:15 UTC2h 5m
2026-07-07 TOR800 - Jul 7, 13:15 UTCJul 7, 14:55 UTC1h 40m
2026-07-07 TOR800 - Jul 7, 11:20 UTCJul 7, 11:35 UTC15m
2026-07-07 TOR800 - Jul 7, 00:05 UTCJul 7, 04:05 UTC4h 0m
2026-07-06 TOR800 - Jul 6, 18:25 UTCJul 6, 23:00 UTC4h 35m
2026-07-06 TOR800 YXE → YYZ Jul 6, 05:50 UTCJul 6, 08:30 UTC2h 40m
2026-07-06 TOR800 - Jul 6, 02:00 UTCJul 6, 04:55 UTC2h 55m
2026-07-05 TOR800 - Jul 5, 23:35 UTCJul 6, 00:20 UTC45m
2026-07-03 TOR800 BZN → YHM Jul 3, 03:15 UTCJul 3, 03:50 UTC35m
2026-07-02 TOR800 BZN → YHM Jul 2, 22:10 UTCJul 3, 02:40 UTC4h 30m
2026-07-02 TOR800 BZN → YHM Jul 2, 15:55 UTCJul 2, 20:45 UTC4h 50m
2026-07-02 TOR800 BZN → YHM Jul 2, 03:35 UTCJul 2, 05:30 UTC1h 55m
2026-07-01 TOR800 BZN → YHM Jul 1, 20:05 UTCJul 2, 02:30 UTC6h 25m
2026-07-01 TOR800 BZN → YHM Jul 1, 01:15 UTCJul 1, 08:15 UTC7h 0m
2026-06-30 TOR800 BZN → YHM Jun 30, 23:40 UTCJul 1, 00:35 UTC55m
2026-06-29 TOR800 BZN → YHM Jun 29, 20:15 UTCJun 30, 03:35 UTC7h 21m
2026-06-29 TOR800 BZN → YHM Jun 29, 02:14 UTCJun 29, 07:40 UTC5h 25m
2026-06-28 TOR800 BZN → YHM Jun 28, 20:59 UTCJun 29, 00:54 UTC3h 55m
2026-06-27 TOR800 BZN → YHM Jun 27, 20:34 UTCJun 27, 21:04 UTC30m
2026-06-27 TOR800 BZN → YHM Jun 27, 13:20 UTCJun 27, 19:24 UTC6h 5m
2026-06-26 TOR800 BZN → YHM Jun 26, 14:05 UTCJun 26, 18:29 UTC4h 25m
2026-06-26 TOR800 BZN → YHM Jun 26, 12:29 UTCJun 26, 12:55 UTC25m
2026-06-24 TOR800 BZN → YHM Jun 24, 08:39 UTCJun 24, 15:24 UTC6h 45m
2026-06-24 TOR800 BZN → YHM Jun 24, 05:59 UTCJun 24, 07:50 UTC1h 50m
2026-06-23 TOR800 BZN → YHM Jun 23, 01:40 UTCJun 23, 10:55 UTC9h 15m
2026-06-22 TOR800 BZN → YHM Jun 22, 21:49 UTCJun 22, 23:39 UTC1h 50m
2026-06-21 TOR800 BZN → YHM Jun 21, 14:50 UTCJun 22, 00:10 UTC9h 20m
2026-06-20 TOR800 BZN → YHM Jun 20, 17:44 UTCJun 20, 17:59 UTC15m
2026-06-20 TOR800 BZN → YHM Jun 20, 11:34 UTCJun 20, 16:59 UTC5h 25m
2026-06-19 TOR800 BZN → YHM Jun 19, 17:14 UTCJun 19, 23:39 UTC6h 25m
2026-06-19 TOR800 BZN → YHM Jun 19, 15:14 UTCJun 19, 16:14 UTC1h 0m
2026-06-19 TOR800 BZN → YHM Jun 19, 11:34 UTCJun 19, 14:19 UTC2h 45m
2026-06-16 TOR800 BZN → YHM Jun 16, 10:49 UTCJun 16, 16:35 UTC5h 45m
2026-06-16 TOR800 BZN → YHM Jun 16, 09:00 UTCJun 16, 09:34 UTC35m
2026-06-16 TOR800 BZN → YHM Jun 16, 01:19 UTCJun 16, 02:00 UTC40m
2026-06-15 TOR800 BZN → YHM Jun 15, 20:15 UTCJun 16, 00:24 UTC4h 10m
2026-06-15 TOR800 BZN → YHM Jun 15, 13:45 UTCJun 15, 18:04 UTC4h 20m
2026-06-14 TOR800 BZN → YHM Jun 14, 21:40 UTCJun 14, 22:10 UTC30m
2026-06-14 TOR800 BZN → YHM Jun 14, 17:35 UTCJun 14, 20:35 UTC3h 0m
2026-06-14 TOR800 BZN → YHM Jun 14, 12:05 UTCJun 14, 15:45 UTC3h 40m

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-FKNN page for operator, model, and routing details .

Mode-S C01BC8 frequently asked

What is Mode-S code C01BC8?
C01BC8 is an ICAO 24-bit transponder address. Allocated to Canada. Assigned to C-FKNN.
Where is Mode-S C01BC8 registered?
Mode-S code C01BC8 is allocated to Canada (CA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is C01BC8 broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex C01BC8, octal 60015710, decimal 12,590,024.
What flights does C01BC8 operate?
Mode-S C01BC8 has broadcast 1 distinct callsign, including TOR800.