sensors Mode-S transponder
C05D79
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GJKI · DASSAULT Falcon 2000 · operated by Irving Air Service Inc.
- Hex
- C05D79
- Octal
- 60056571
- Decimal
- 12,606,841
- Country
- CA
- Tail
- C-GJKI
- Type
- F2TH
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address C05D79 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 |
|---|---|---|---|
| CGJKI | - | 48 | 2026-05-28 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | CGJKI | - | May 28, 21:15 UTC | May 28, 21:30 UTC | 15m |
| 2026-05-28 | CGJKI | - | May 28, 17:45 UTC | May 28, 20:50 UTC | 3h 5m |
| 2026-05-28 | CGJKI | YSJ → BGR | May 28, 16:10 UTC | May 28, 17:20 UTC | 1h 10m |
| 2026-05-27 | CGJKI | - | May 27, 19:25 UTC | May 27, 20:40 UTC | 1h 15m |
| 2026-05-27 | CGJKI | - | May 27, 17:25 UTC | May 27, 18:40 UTC | 1h 15m |
| 2026-05-27 | CGJKI | - | May 27, 12:05 UTC | May 27, 13:05 UTC | 1h 0m |
| 2026-05-27 | CGJKI | - | May 27, 10:15 UTC | May 27, 10:25 UTC | 10m |
| 2026-05-27 | CGJKI | - | May 27, 01:19 UTC | May 27, 02:39 UTC | 1h 20m |
| 2026-05-26 | CGJKI | - | May 26, 22:50 UTC | May 27, 00:39 UTC | 1h 50m |
| 2026-05-26 | CGJKI | - | May 26, 21:14 UTC | May 26, 21:25 UTC | 10m |
| 2026-05-26 | CGJKI | - | May 26, 19:10 UTC | May 26, 20:00 UTC | 50m |
| 2026-05-26 | CGJKI | - | May 26, 17:20 UTC | May 26, 18:10 UTC | 50m |
| 2026-05-26 | CGJKI | BED → YSJ | May 26, 11:39 UTC | May 26, 12:30 UTC | 50m |
| 2026-05-26 | CGJKI | - | May 26, 10:10 UTC | May 26, 11:05 UTC | 55m |
| 2026-05-25 | CGJKI | - | May 25, 21:40 UTC | May 25, 21:54 UTC | 15m |
| 2026-05-25 | CGJKI | - | May 25, 13:30 UTC | May 25, 14:45 UTC | 1h 15m |
| 2026-05-25 | CGJKI | - | May 25, 10:20 UTC | May 25, 12:10 UTC | 1h 50m |
| 2026-05-18 | CGJKI | YYZ → YSJ | May 18, 13:25 UTC | May 18, 15:40 UTC | 2h 15m |
| 2026-05-17 | CGJKI | - | May 17, 19:01 UTC | May 17, 20:45 UTC | 1h 45m |
| 2026-05-14 | CGJKI | - | May 14, 21:30 UTC | May 14, 22:55 UTC | 1h 25m |
| 2026-05-14 | CGJKI | - | May 14, 16:05 UTC | May 14, 17:50 UTC | 1h 45m |
| 2026-05-13 | CGJKI | - | May 13, 15:35 UTC | May 13, 16:00 UTC | 25m |
| 2026-05-12 | CGJKI | - | May 12, 20:45 UTC | May 12, 21:05 UTC | 20m |
| 2026-05-12 | CGJKI | - | May 12, 09:10 UTC | May 12, 11:35 UTC | 2h 25m |
| 2026-05-09 | CGJKI | - | May 9, 17:35 UTC | May 9, 17:49 UTC | 15m |
| 2026-05-09 | CGJKI | - | May 9, 15:30 UTC | May 9, 16:20 UTC | 50m |
| 2026-05-09 | CGJKI | - | May 9, 11:40 UTC | May 9, 12:30 UTC | 50m |
| 2026-05-03 | CGJKI | BED → YSJ | May 3, 19:40 UTC | May 3, 20:30 UTC | 50m |
| 2026-05-01 | CGJKI | - | May 1, 18:05 UTC | May 1, 19:00 UTC | 55m |
| 2026-05-01 | CGJKI | - | May 1, 12:35 UTC | May 1, 13:20 UTC | 45m |
| 2026-04-28 | CGJKI | - | Apr 28, 19:45 UTC | Apr 28, 20:35 UTC | 50m |
| 2026-04-24 | CGJKI | - | Apr 24, 20:10 UTC | Apr 24, 21:10 UTC | 1h 0m |
| 2026-04-24 | CGJKI | - | Apr 24, 15:45 UTC | Apr 24, 16:10 UTC | 25m |
| 2026-04-23 | CGJKI | YYZ → YUL | Apr 23, 13:45 UTC | Apr 23, 14:35 UTC | 50m |
| 2026-04-22 | CGJKI | - | Apr 22, 13:25 UTC | Apr 22, 15:05 UTC | 1h 40m |
| 2026-04-21 | CGJKI | - | Apr 21, 20:10 UTC | Apr 21, 21:00 UTC | 50m |
| 2026-04-21 | CGJKI | - | Apr 21, 15:45 UTC | Apr 21, 16:40 UTC | 55m |
| 2026-04-21 | CGJKI | - | Apr 21, 14:45 UTC | Apr 21, 15:01 UTC | 15m |
| 2026-04-19 | CGJKI | BED → YSJ | Apr 19, 19:45 UTC | Apr 19, 20:35 UTC | 50m |
| 2026-04-17 | CGJKI | - | Apr 17, 20:35 UTC | Apr 17, 21:20 UTC | 45m |
| 2026-04-15 | CGJKI | - | Apr 15, 22:00 UTC | Apr 15, 22:20 UTC | 20m |
| 2026-04-15 | CGJKI | - | Apr 15, 21:05 UTC | Apr 15, 21:25 UTC | 20m |
| 2026-04-15 | CGJKI | - | Apr 15, 20:40 UTC | Apr 15, 21:00 UTC | 20m |
| 2026-04-14 | CGJKI | - | Apr 14, 19:15 UTC | Apr 14, 20:00 UTC | 45m |
| 2026-04-14 | CGJKI | - | Apr 14, 14:50 UTC | Apr 14, 15:40 UTC | 50m |
| 2026-04-13 | CGJKI | - | Apr 13, 16:20 UTC | Apr 13, 17:25 UTC | 1h 5m |
| 2026-04-13 | CGJKI | - | Apr 13, 15:30 UTC | Apr 13, 15:45 UTC | 15m |
| 2026-04-12 | CGJKI | - | Apr 12, 17:15 UTC | Apr 12, 19:30 UTC | 2h 15m |
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-GJKI page for operator, model, and routing details .