sensors Mode-S transponder
C05212
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GFCB · BOMBARDIER CL-600 Challenger · operated by I.M.P. GROUP LIMITED (EXECAIRE)
- Hex
- C05212
- Octal
- 60051022
- Decimal
- 12,603,922
- Country
- CA
- Tail
- C-GFCB
- Type
- CL60
- Flights observed
- 44
- Distinct callsigns
- 4
- Country
- CA
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address C05212 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 4 distinct
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-20 | CGPGB | - | Jun 20, 17:14 UTC | Jun 20, 22:10 UTC | 4h 55m |
| 2026-06-19 | 00000000 | - | Jun 19, 17:04 UTC | Jun 19, 20:55 UTC | 3h 50m |
| 2026-06-18 | CGPGB | - | Jun 18, 17:05 UTC | Jun 18, 18:30 UTC | 1h 25m |
| 2026-06-18 | CGFCB | - | Jun 18, 12:30 UTC | Jun 18, 17:00 UTC | 4h 30m |
| 2026-06-16 | CGFCB | - | Jun 16, 22:25 UTC | Jun 16, 23:20 UTC | 55m |
| 2026-06-16 | CGFCB | - | Jun 16, 16:55 UTC | Jun 16, 17:49 UTC | 55m |
| 2026-06-16 | CGPGB | YYZ → YQY | Jun 16, 14:45 UTC | Jun 16, 16:45 UTC | 2h 0m |
| 2026-06-11 | CGPGB | PWK → YYZ | Jun 11, 18:15 UTC | Jun 11, 19:25 UTC | 1h 10m |
| 2026-06-11 | CGPGB | YYZ → PWK | Jun 11, 13:20 UTC | Jun 11, 14:30 UTC | 1h 10m |
| 2026-06-09 | CGFCB | - | Jun 9, 19:45 UTC | Jun 9, 20:35 UTC | 50m |
| 2026-06-09 | CGPGB | - | Jun 9, 17:40 UTC | Jun 9, 19:30 UTC | 1h 50m |
| 2026-06-09 | CGPGB | - | Jun 9, 14:00 UTC | Jun 9, 14:10 UTC | 10m |
| 2026-06-07 | CGFCB | - | Jun 7, 20:20 UTC | Jun 7, 21:15 UTC | 55m |
| 2026-06-07 | CGPGB | - | Jun 7, 13:15 UTC | Jun 7, 14:55 UTC | 1h 40m |
| 2026-06-03 | CGPGB | - | Jun 3, 17:50 UTC | Jun 3, 21:55 UTC | 4h 5m |
| 2026-06-02 | CGPGB | - | Jun 2, 01:25 UTC | Jun 2, 01:40 UTC | 15m |
| 2026-06-01 | CGPGB | - | Jun 1, 13:45 UTC | Jun 1, 17:55 UTC | 4h 10m |
| 2026-05-31 | CGPGB | YYZ → YYZ | May 31, 16:55 UTC | May 31, 17:20 UTC | 25m |
| 2026-05-29 | CGFCB | - | May 29, 17:05 UTC | May 29, 19:35 UTC | 2h 30m |
| 2026-05-28 | CGFCB | - | May 28, 13:55 UTC | May 28, 16:35 UTC | 2h 40m |
| 2026-05-20 | CGFCB | - | May 20, 21:45 UTC | May 20, 22:45 UTC | 1h 0m |
| 2026-05-19 | 00000000 | YYZ → MDW | May 19, 15:30 UTC | May 19, 16:45 UTC | 1h 15m |
| 2026-05-19 | 00000000 | - | May 19, 13:40 UTC | May 19, 14:45 UTC | 1h 5m |
| 2026-05-19 | 00000000 | YYZ → ZBM | May 19, 10:45 UTC | May 19, 11:40 UTC | 55m |
| 2026-05-14 | CGFCB | - | May 14, 19:10 UTC | May 15, 00:50 UTC | 5h 40m |
| 2026-05-12 | 00000000 | YYZ → BFI | May 12, 17:25 UTC | May 12, 22:01 UTC | 4h 35m |
| 2026-05-11 | 00000000 | - | May 11, 02:30 UTC | May 11, 03:35 UTC | 1h 5m |
| 2026-05-10 | 00000000 | - | May 10, 19:05 UTC | May 10, 20:00 UTC | 55m |
| 2026-05-08 | CGFCB | - | May 8, 20:15 UTC | May 9, 00:30 UTC | 4h 15m |
| 2026-05-06 | 00000000 | IAD → APC | May 6, 16:50 UTC | May 6, 22:15 UTC | 5h 25m |
| 2026-05-05 | 00000000 | YYZ → IAD | May 5, 14:10 UTC | May 5, 15:05 UTC | 55m |
| 2026-05-04 | CGFCB | - | May 4, 19:25 UTC | May 5, 00:25 UTC | 5h 0m |
| 2026-04-29 | CGFCB | - | Apr 29, 16:55 UTC | Apr 29, 17:15 UTC | 20m |
| 2026-04-29 | CGFCB | - | Apr 29, 12:30 UTC | Apr 29, 16:25 UTC | 3h 55m |
| 2026-04-27 | CG000000 | - | Apr 27, 21:05 UTC | Apr 27, 21:45 UTC | 40m |
| 2026-04-27 | CG000000 | - | Apr 27, 02:40 UTC | Apr 27, 03:05 UTC | 25m |
| 2026-04-26 | CG000000 | - | Apr 26, 20:40 UTC | Apr 26, 21:30 UTC | 50m |
| 2026-04-25 | 00000000 | - | Apr 25, 20:30 UTC | Apr 25, 22:10 UTC | 1h 40m |
| 2026-04-24 | 00000000 | - | Apr 24, 13:50 UTC | Apr 24, 14:30 UTC | 40m |
| 2026-04-24 | 00000000 | - | Apr 24, 11:30 UTC | Apr 24, 13:10 UTC | 1h 40m |
| 2026-04-23 | CGFCB | - | Apr 23, 20:45 UTC | Apr 23, 21:50 UTC | 1h 5m |
| 2026-04-16 | CGFCB | - | Apr 16, 03:09 UTC | Apr 16, 03:49 UTC | 40m |
| 2026-04-16 | CGFCB | - | Apr 16, 02:50 UTC | Apr 16, 03:04 UTC | 15m |
| 2026-04-15 | CGFCB | YYZ → IAD | Apr 15, 17:25 UTC | Apr 15, 18:15 UTC | 50m |
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-GFCB page for operator, model, and routing details .