sensors Mode-S transponder

C05D5C

ICAO 24-bit transponder address · allocated to Canada

Currently assigned to C-GJJF · BEECH 100 King Air · operated by Propair Inc.

Hex
C05D5C
Octal
60056534
Decimal
12,606,812
Country
CA
Tail
C-GJJF
Type
BE10
No current signal · last broadcast 1d ago
Flights observed
66
Distinct callsigns
20
Country
CA
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S C05D5C.

Country allocation

The ICAO 24-bit address C05D5C 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 20 distinct

Callsign Airline Flights Last seen
PRO4700M - 8 2026-07-01
PRO4450 Propair 7 2026-07-10
PRO4215M - 7 2026-06-16
PRO4200M - 4 2026-06-18
PRO4830 - 3 2026-07-06
PRO4821 - 3 2026-07-05
PRO4510 - 3 2026-06-22
PRO4451 Propair 3 2026-07-09
PRO4600 Propair 2 2026-06-26
PRO4350 Propair 2 2026-05-29
PRO4230M - 2 2026-06-13
PRO4150M - 2 2026-07-01
PRO1075 Propair 2 2026-05-29
PR04823 - 2 2026-06-18
PRO4865 - 1 2026-06-23
PRO4863 - 1 2026-06-23
PRO4860 - 1 2026-07-13
PRO4858 - 1 2026-07-13
PRO4825 - 1 2026-07-13
PRO4511 - 1 2026-06-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 PRO4825 - Jul 13, 13:20 UTCJul 13, 14:40 UTC1h 20m
2026-07-13 PRO4860 - Jul 13, 11:55 UTCJul 13, 12:30 UTC35m
2026-07-13 PRO4858 - Jul 13, 09:20 UTCJul 13, 11:25 UTC2h 5m
2026-07-10 PRO4450 YVO → YTZ Jul 10, 19:05 UTCJul 10, 20:20 UTC1h 15m
2026-07-10 PRO4450 YVO → YTZ Jul 10, 17:05 UTCJul 10, 18:20 UTC1h 15m
2026-07-09 PRO4451 YTZ → YUY Jul 9, 20:10 UTCJul 9, 21:25 UTC1h 15m
2026-07-09 PRO4450 YVO → YTZ Jul 9, 17:20 UTCJul 9, 18:35 UTC1h 15m
2026-07-09 PRO4458 - Jul 9, 13:05 UTCJul 9, 14:20 UTC1h 15m
2026-07-09 PRO4457 - Jul 9, 11:25 UTCJul 9, 13:00 UTC1h 35m
2026-07-08 PRO4450 YVO → YTZ Jul 8, 14:15 UTCJul 8, 14:25 UTC10m
2026-07-07 PRO4451 YTZ → YUY Jul 7, 17:30 UTCJul 7, 17:45 UTC15m
2026-07-07 PRO4450 YVO → YTZ Jul 7, 16:05 UTCJul 7, 16:25 UTC20m
2026-07-07 PRO4450 YVO → YTZ Jul 7, 14:00 UTCJul 7, 15:05 UTC1h 5m
2026-07-06 PRO4830 - Jul 6, 23:10 UTCJul 7, 02:05 UTC2h 55m
2026-07-06 PRO4830 - Jul 6, 21:15 UTCJul 6, 22:30 UTC1h 15m
2026-07-06 PRO4451 YTZ → YUY Jul 6, 12:40 UTCJul 6, 13:50 UTC1h 10m
2026-07-06 PRO4450 YVO → YTZ Jul 6, 10:45 UTCJul 6, 12:00 UTC1h 15m
2026-07-05 PRO4821 - Jul 5, 21:30 UTCJul 5, 21:55 UTC25m
2026-07-05 PRO4821 - Jul 5, 20:15 UTCJul 5, 20:55 UTC40m
2026-07-05 PRO4821 - Jul 5, 14:00 UTCJul 5, 15:15 UTC1h 15m
2026-07-02 PRO4275M - Jul 2, 14:45 UTCJul 2, 16:05 UTC1h 20m
2026-07-01 PRO4700M - Jul 1, 19:40 UTCJul 1, 20:35 UTC55m
2026-07-01 PRO4700M - Jul 1, 15:05 UTCJul 1, 16:15 UTC1h 10m
2026-07-01 PRO4700M - Jul 1, 12:20 UTCJul 1, 13:35 UTC1h 15m
2026-07-01 PRO4700M - Jul 1, 11:50 UTCJul 1, 12:05 UTC15m
2026-07-01 PRO4150M - Jul 1, 01:15 UTCJul 1, 02:40 UTC1h 25m
2026-06-30 PRO4150M - Jun 30, 21:30 UTCJun 30, 22:40 UTC1h 10m
2026-06-28 PRO4700M - Jun 28, 20:45 UTCJun 28, 21:55 UTC1h 10m
2026-06-28 PRO4700M - Jun 28, 18:14 UTCJun 28, 18:59 UTC45m
2026-06-28 PRO4700M - Jun 28, 14:09 UTCJun 28, 15:14 UTC1h 5m
2026-06-28 PRO4700M - Jun 28, 11:39 UTCJun 28, 12:55 UTC1h 15m
2026-06-26 PRO4600 YUY → YHU Jun 26, 12:14 UTCJun 26, 12:24 UTC10m
2026-06-25 PRO4600 YUY → YHU Jun 25, 13:35 UTCJun 25, 13:50 UTC15m
2026-06-24 PRO4050 YUY → YYZ Jun 24, 14:09 UTCJun 24, 14:24 UTC15m
2026-06-23 PRO1005 YUY → YSB Jun 23, 02:15 UTCJun 23, 02:45 UTC30m
2026-06-23 PRO4865 - Jun 23, 00:54 UTCJun 23, 02:04 UTC1h 10m
2026-06-23 PRO4863 - Jun 23, 00:00 UTCJun 23, 00:24 UTC25m
2026-06-22 PRO4830 - Jun 22, 22:15 UTCJun 22, 23:35 UTC1h 20m
2026-06-22 PRO4511 - Jun 22, 17:55 UTCJun 22, 18:24 UTC30m
2026-06-22 PRO4510 - Jun 22, 16:45 UTCJun 22, 17:04 UTC20m
2026-06-22 PRO4510 - Jun 22, 15:35 UTCJun 22, 15:54 UTC20m
2026-06-22 PRO4510 - Jun 22, 14:40 UTCJun 22, 14:59 UTC20m
2026-06-21 PRO4260M - Jun 21, 00:04 UTCJun 21, 00:19 UTC15m
2026-06-18 PR04899 - Jun 18, 23:45 UTCJun 19, 00:14 UTC29m
2026-06-18 PR04893 - Jun 18, 22:30 UTCJun 18, 23:10 UTC40m
2026-06-18 PR04823 - Jun 18, 21:20 UTCJun 18, 21:55 UTC35m
2026-06-18 PR04823 - Jun 18, 20:15 UTCJun 18, 20:35 UTC20m
2026-06-18 PRO4200M - Jun 18, 02:40 UTCJun 18, 03:50 UTC1h 10m
2026-06-18 PRO4200M - Jun 18, 00:10 UTCJun 18, 00:55 UTC45m
2026-06-17 PRO4245M - Jun 17, 02:55 UTCJun 17, 03:15 UTC20m

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

Mode-S C05D5C frequently asked

What is Mode-S code C05D5C?
C05D5C is an ICAO 24-bit transponder address. Allocated to Canada. Assigned to C-GJJF.
Where is Mode-S C05D5C registered?
Mode-S code C05D5C is allocated to Canada (CA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is C05D5C broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex C05D5C, octal 60056534, decimal 12,606,812.
What flights does C05D5C operate?
Mode-S C05D5C has broadcast 20 distinct callsigns, including PRO4700M, PRO4450, PRO4215M, PRO4200M, PRO4830.