sensors Mode-S transponder
C005B3
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FCEC · BOMBARDIER BD-100 Challenger 350 · operated by Sunwest Aviation Ltd.
- Hex
- C005B3
- Octal
- 60002663
- Decimal
- 12,584,371
- Country
- CA
- Tail
- C-FCEC
- Type
- CL35
- Flights observed
- 56
- Distinct callsigns
- 2
- Country
- CA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C005B3 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | CNK5 | YYC → YYC | May 28, 13:00 UTC | May 28, 23:00 UTC | 10h 0m |
| 2026-05-28 | CNK5 | - | May 28, 02:35 UTC | May 28, 04:50 UTC | 2h 15m |
| 2026-05-27 | CNK5 | - | May 27, 18:30 UTC | May 27, 20:50 UTC | 2h 20m |
| 2026-05-26 | CNK5 | - | May 26, 21:00 UTC | May 26, 22:05 UTC | 1h 5m |
| 2026-05-26 | CNK5 | - | May 26, 16:45 UTC | May 26, 17:50 UTC | 1h 5m |
| 2026-05-25 | CNK5 | - | May 25, 13:30 UTC | May 25, 14:00 UTC | 30m |
| 2026-05-25 | CNK5 | - | May 25, 12:15 UTC | May 25, 12:45 UTC | 30m |
| 2026-05-24 | CNK5 | - | May 24, 03:40 UTC | May 24, 04:30 UTC | 50m |
| 2026-05-23 | CNK5 | YYC → YXE | May 23, 19:35 UTC | May 23, 20:25 UTC | 50m |
| 2026-05-21 | CNK5 | - | May 21, 16:15 UTC | May 21, 19:50 UTC | 3h 35m |
| 2026-05-20 | CNK5 | YYC → YYZ | May 20, 00:05 UTC | May 20, 03:30 UTC | 3h 25m |
| 2026-05-18 | CNK5 | - | May 18, 20:10 UTC | May 19, 00:00 UTC | 3h 50m |
| 2026-05-18 | CNK5 | - | May 18, 15:55 UTC | May 18, 19:00 UTC | 3h 4m |
| 2026-05-15 | CNK5 | - | May 15, 17:20 UTC | May 15, 18:45 UTC | 1h 25m |
| 2026-05-12 | CNK5 | - | May 12, 15:50 UTC | May 12, 17:05 UTC | 1h 15m |
| 2026-05-12 | CNK5 | YYC → GEG | May 12, 14:05 UTC | May 12, 14:55 UTC | 50m |
| 2026-05-11 | CNK5 | YVR → YYC | May 11, 18:40 UTC | May 11, 19:40 UTC | 1h 0m |
| 2026-05-11 | CNK5 | - | May 11, 17:45 UTC | May 11, 18:10 UTC | 25m |
| 2026-05-11 | CNK5 | - | May 11, 12:50 UTC | May 11, 13:00 UTC | 10m |
| 2026-05-11 | CNK5 | - | May 11, 00:05 UTC | May 11, 00:40 UTC | 35m |
| 2026-05-10 | CNK5 | - | May 10, 18:45 UTC | May 10, 19:19 UTC | 35m |
| 2026-05-09 | CNK5 | - | May 9, 19:05 UTC | May 9, 20:15 UTC | 1h 10m |
| 2026-05-08 | CNK5 | - | May 8, 21:00 UTC | May 9, 00:50 UTC | 3h 50m |
| 2026-05-08 | CNK5 | - | May 8, 19:15 UTC | May 8, 20:20 UTC | 1h 5m |
| 2026-05-07 | CNK5 | CMH → YSJ | May 7, 23:49 UTC | May 8, 01:40 UTC | 1h 50m |
| 2026-05-07 | CNK5 | YYC → CMH | May 7, 20:00 UTC | May 7, 23:05 UTC | 3h 4m |
| 2026-05-05 | CNK5 | - | May 5, 20:01 UTC | May 5, 20:45 UTC | 45m |
| 2026-05-05 | CNK5 | - | May 5, 14:05 UTC | May 5, 14:40 UTC | 35m |
| 2026-05-04 | 00000000 | - | May 4, 17:50 UTC | May 4, 21:40 UTC | 3h 51m |
| 2026-05-04 | 00000000 | - | May 4, 15:05 UTC | May 4, 15:55 UTC | 50m |
| 2026-05-03 | 00000000 | YYC → BOS | May 3, 18:05 UTC | May 3, 22:15 UTC | 4h 10m |
| 2026-05-03 | 00000000 | YWG → YYC | May 3, 01:55 UTC | May 3, 03:40 UTC | 1h 44m |
| 2026-05-02 | 00000000 | YYC → YWG | May 2, 15:05 UTC | May 2, 16:40 UTC | 1h 35m |
| 2026-04-28 | 00000000 | YYC → YYC | Apr 28, 15:05 UTC | Apr 29, 00:30 UTC | 9h 25m |
| 2026-04-24 | 00000000 | - | Apr 24, 23:35 UTC | Apr 25, 03:20 UTC | 3h 45m |
| 2026-04-24 | 00000000 | - | Apr 24, 20:35 UTC | Apr 24, 22:45 UTC | 2h 10m |
| 2026-04-24 | 00000000 | - | Apr 24, 18:15 UTC | Apr 24, 20:00 UTC | 1h 45m |
| 2026-04-23 | 00000000 | - | Apr 23, 18:30 UTC | Apr 23, 18:45 UTC | 15m |
| 2026-04-22 | 00000000 | - | Apr 22, 19:35 UTC | Apr 22, 20:50 UTC | 1h 15m |
| 2026-04-21 | 00000000 | - | Apr 21, 20:30 UTC | Apr 21, 21:55 UTC | 1h 25m |
| 2026-04-20 | 00000000 | - | Apr 20, 22:40 UTC | Apr 20, 23:10 UTC | 30m |
| 2026-04-18 | 00000000 | - | Apr 18, 18:00 UTC | Apr 18, 22:25 UTC | 4h 25m |
| 2026-04-18 | 00000000 | - | Apr 18, 01:25 UTC | Apr 18, 01:40 UTC | 15m |
| 2026-04-18 | 00000000 | - | Apr 18, 00:50 UTC | Apr 18, 22:25 UTC | 21h 35m |
| 2026-04-17 | 00000000 | - | Apr 17, 23:25 UTC | Apr 18, 01:10 UTC | 1h 45m |
| 2026-04-17 | 00000000 | - | Apr 17, 23:05 UTC | Apr 18, 22:25 UTC | 23h 20m |
| 2026-04-17 | 00000000 | - | Apr 17, 21:25 UTC | Apr 17, 22:10 UTC | 45m |
| 2026-04-17 | 00000000 | - | Apr 17, 19:30 UTC | Apr 17, 21:20 UTC | 1h 50m |
| 2026-04-17 | 00000000 | - | Apr 17, 01:20 UTC | Apr 17, 01:40 UTC | 20m |
| 2026-04-17 | 00000000 | - | Apr 17, 00:30 UTC | Apr 17, 01:15 UTC | 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-FCEC page for operator, model, and routing details .