sensors Mode-S transponder
C05CC3
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GJDI · BEECH 200 Super King Air · operated by Irving Air Service Inc.
- Hex
- C05CC3
- Octal
- 60056303
- Decimal
- 12,606,659
- Country
- CA
- Tail
- C-GJDI
- Type
- BE20
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address C05CC3 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 |
|---|---|---|---|
| CGJDI | - | 66 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CGJDI | - | Jul 13, 19:30 UTC | Jul 13, 19:50 UTC | 20m |
| 2026-07-13 | CGJDI | - | Jul 13, 18:15 UTC | Jul 13, 18:30 UTC | 15m |
| 2026-07-11 | CGJDI | - | Jul 11, 19:00 UTC | Jul 11, 19:20 UTC | 20m |
| 2026-07-11 | CGJDI | - | Jul 11, 18:10 UTC | Jul 11, 18:25 UTC | 15m |
| 2026-07-11 | CGJDI | - | Jul 11, 15:50 UTC | Jul 11, 16:10 UTC | 20m |
| 2026-07-10 | CGJDI | - | Jul 10, 19:25 UTC | Jul 10, 19:40 UTC | 15m |
| 2026-07-09 | CGJDI | - | Jul 9, 19:50 UTC | Jul 9, 20:05 UTC | 15m |
| 2026-07-09 | CGJDI | - | Jul 9, 12:05 UTC | Jul 9, 12:25 UTC | 20m |
| 2026-07-07 | CGJDI | - | Jul 7, 15:05 UTC | Jul 7, 15:55 UTC | 50m |
| 2026-07-05 | CGJDI | - | Jul 5, 18:45 UTC | Jul 5, 19:45 UTC | 1h 0m |
| 2026-07-04 | CGJDI | - | Jul 4, 19:15 UTC | Jul 4, 19:25 UTC | 10m |
| 2026-07-04 | CGJDI | - | Jul 4, 18:20 UTC | Jul 4, 18:30 UTC | 10m |
| 2026-07-03 | CGJDI | - | Jul 3, 20:00 UTC | Jul 3, 20:20 UTC | 20m |
| 2026-06-26 | CGJDI | - | Jun 26, 20:10 UTC | Jun 26, 21:15 UTC | 1h 5m |
| 2026-06-26 | CGJDI | - | Jun 26, 15:29 UTC | Jun 26, 15:45 UTC | 15m |
| 2026-06-24 | CGJDI | - | Jun 24, 18:55 UTC | Jun 24, 19:34 UTC | 40m |
| 2026-06-24 | CGJDI | - | Jun 24, 11:34 UTC | Jun 24, 12:09 UTC | 35m |
| 2026-06-21 | CGJDI | - | Jun 21, 01:45 UTC | Jun 21, 01:59 UTC | 15m |
| 2026-06-20 | CGJDI | - | Jun 20, 23:55 UTC | Jun 21, 01:10 UTC | 1h 15m |
| 2026-06-20 | CGJDI | - | Jun 20, 17:54 UTC | Jun 20, 20:05 UTC | 2h 10m |
| 2026-06-20 | CGJDI | - | Jun 20, 16:39 UTC | Jun 20, 16:55 UTC | 15m |
| 2026-06-17 | CGJDI | - | Jun 17, 20:25 UTC | Jun 17, 20:35 UTC | 10m |
| 2026-06-17 | CGJDI | - | Jun 17, 15:00 UTC | Jun 17, 15:20 UTC | 20m |
| 2026-06-14 | CGJDI | - | Jun 14, 14:50 UTC | Jun 14, 15:05 UTC | 15m |
| 2026-06-13 | CGJDI | - | Jun 13, 19:55 UTC | Jun 13, 20:10 UTC | 15m |
| 2026-06-12 | CGJDI | BOS → YSJ | Jun 12, 15:00 UTC | Jun 12, 16:05 UTC | 1h 5m |
| 2026-06-12 | CGJDI | - | Jun 12, 12:30 UTC | Jun 12, 13:45 UTC | 1h 15m |
| 2026-06-11 | CGJDI | BOS → YSJ | Jun 11, 16:05 UTC | Jun 11, 17:10 UTC | 1h 5m |
| 2026-06-11 | CGJDI | - | Jun 11, 13:05 UTC | Jun 11, 14:15 UTC | 1h 10m |
| 2026-06-09 | CGJDI | - | Jun 9, 12:45 UTC | Jun 9, 13:40 UTC | 55m |
| 2026-06-09 | CGJDI | - | Jun 9, 11:50 UTC | Jun 9, 12:15 UTC | 25m |
| 2026-06-06 | CGJDI | - | Jun 6, 19:54 UTC | Jun 6, 20:05 UTC | 10m |
| 2026-06-06 | CGJDI | - | Jun 6, 19:04 UTC | Jun 6, 19:24 UTC | 20m |
| 2026-06-06 | CGJDI | - | Jun 6, 12:49 UTC | Jun 6, 13:05 UTC | 15m |
| 2026-06-06 | CGJDI | - | Jun 6, 10:55 UTC | Jun 6, 11:09 UTC | 15m |
| 2026-06-05 | CGJDI | YSJ → YSJ | Jun 5, 16:10 UTC | Jun 5, 17:05 UTC | 55m |
| 2026-06-02 | CGJDI | - | Jun 2, 00:40 UTC | Jun 2, 00:55 UTC | 15m |
| 2026-06-01 | CGJDI | - | Jun 1, 20:30 UTC | Jun 1, 20:45 UTC | 15m |
| 2026-05-29 | CGJDI | - | May 29, 01:00 UTC | May 29, 01:50 UTC | 50m |
| 2026-05-28 | CGJDI | - | May 28, 19:25 UTC | May 28, 20:05 UTC | 40m |
| 2026-05-28 | CGJDI | - | May 28, 12:25 UTC | May 28, 13:50 UTC | 1h 25m |
| 2026-05-28 | CGJDI | - | May 28, 11:30 UTC | May 28, 12:10 UTC | 40m |
| 2026-05-20 | CGJDI | - | May 20, 20:35 UTC | May 20, 20:50 UTC | 15m |
| 2026-05-20 | CGJDI | - | May 20, 13:10 UTC | May 20, 13:20 UTC | 10m |
| 2026-05-19 | CGJDI | - | May 19, 17:30 UTC | May 19, 17:55 UTC | 25m |
| 2026-05-19 | CGJDI | - | May 19, 13:05 UTC | May 19, 13:20 UTC | 15m |
| 2026-05-18 | CGJDI | - | May 18, 20:45 UTC | May 18, 21:55 UTC | 1h 10m |
| 2026-05-18 | CGJDI | - | May 18, 15:40 UTC | May 18, 17:00 UTC | 1h 20m |
| 2026-05-15 | CGJDI | - | May 15, 11:55 UTC | May 15, 12:20 UTC | 25m |
| 2026-05-14 | CGJDI | - | May 14, 18:50 UTC | May 14, 19:45 UTC | 55m |
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-GJDI page for operator, model, and routing details .