sensors Mode-S transponder
C05AFF
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GILY · PIPER PA-44 Seminole · operated by Pacific Professional Flight Centre Ltd
- Hex
- C05AFF
- Octal
- 60055377
- Decimal
- 12,606,207
- Country
- CA
- Tail
- C-GILY
- Type
- PA44
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address C05AFF 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 |
|---|---|---|---|
| CGILY | - | 54 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CGILY | YDT → YDT | Jul 13, 20:40 UTC | Jul 13, 21:30 UTC | 50m |
| 2026-07-13 | CGILY | YDT → YDT | Jul 13, 18:50 UTC | Jul 13, 19:35 UTC | 45m |
| 2026-07-13 | CGILY | - | Jul 13, 16:15 UTC | Jul 13, 17:15 UTC | 1h 0m |
| 2026-07-10 | CGILY | - | Jul 10, 18:10 UTC | Jul 10, 19:20 UTC | 1h 10m |
| 2026-07-10 | CGILY | - | Jul 10, 16:10 UTC | Jul 10, 17:00 UTC | 50m |
| 2026-07-08 | CGILY | - | Jul 8, 19:40 UTC | Jul 8, 20:35 UTC | 55m |
| 2026-07-06 | CGILY | YDT → YDT | Jul 6, 18:55 UTC | Jul 6, 19:45 UTC | 50m |
| 2026-07-06 | CGILY | YDT → YDT | Jul 6, 16:40 UTC | Jul 6, 17:40 UTC | 1h 0m |
| 2026-07-03 | CGILY | - | Jul 3, 18:55 UTC | Jul 3, 19:45 UTC | 50m |
| 2026-07-01 | CGILY | - | Jul 1, 17:45 UTC | Jul 1, 18:30 UTC | 45m |
| 2026-06-30 | CGILY | - | Jun 30, 22:40 UTC | Jun 30, 23:00 UTC | 20m |
| 2026-06-30 | CGILY | - | Jun 30, 01:40 UTC | Jun 30, 02:25 UTC | 45m |
| 2026-06-29 | CGILY | - | Jun 29, 22:44 UTC | Jun 29, 23:34 UTC | 50m |
| 2026-06-29 | CGILY | YDT → YDT | Jun 29, 16:39 UTC | Jun 29, 17:34 UTC | 55m |
| 2026-06-28 | CGILY | YDT → YDT | Jun 28, 20:39 UTC | Jun 28, 21:30 UTC | 50m |
| 2026-06-26 | CGILY | YDT → YDT | Jun 26, 03:00 UTC | Jun 26, 03:50 UTC | 50m |
| 2026-06-24 | CGILY | YDT → YDT | Jun 24, 23:45 UTC | Jun 25, 00:44 UTC | 1h 0m |
| 2026-06-22 | CGILY | - | Jun 22, 23:05 UTC | Jun 23, 00:00 UTC | 55m |
| 2026-06-22 | CGILY | - | Jun 22, 19:54 UTC | Jun 22, 20:55 UTC | 1h 0m |
| 2026-06-20 | CGILY | YDT → YDT | Jun 20, 16:49 UTC | Jun 20, 17:39 UTC | 50m |
| 2026-06-19 | CGILY | YDT → YDT | Jun 19, 19:09 UTC | Jun 19, 20:29 UTC | 1h 20m |
| 2026-06-17 | CGILY | YDT → YDT | Jun 17, 14:35 UTC | Jun 17, 15:50 UTC | 1h 15m |
| 2026-06-12 | CGILY | - | Jun 12, 16:55 UTC | Jun 12, 17:50 UTC | 55m |
| 2026-06-11 | CGILY | - | Jun 11, 18:40 UTC | Jun 11, 19:30 UTC | 50m |
| 2026-06-11 | CGILY | - | Jun 11, 14:55 UTC | Jun 11, 15:50 UTC | 55m |
| 2026-06-09 | CGILY | - | Jun 9, 19:00 UTC | Jun 9, 19:55 UTC | 55m |
| 2026-06-08 | CGILY | - | Jun 8, 16:20 UTC | Jun 8, 17:05 UTC | 45m |
| 2026-06-06 | CGILY | YDT → YDT | Jun 6, 18:50 UTC | Jun 6, 19:54 UTC | 1h 5m |
| 2026-06-01 | CGILY | YDT → YDT | Jun 1, 19:10 UTC | Jun 1, 20:00 UTC | 50m |
| 2026-06-01 | CGILY | YDT → YDT | Jun 1, 16:40 UTC | Jun 1, 17:40 UTC | 1h 0m |
| 2026-05-28 | CGILY | - | May 28, 20:25 UTC | May 28, 21:15 UTC | 50m |
| 2026-05-21 | CGILY | YDT → YDT | May 21, 18:40 UTC | May 21, 19:45 UTC | 1h 5m |
| 2026-05-20 | CGILY | - | May 20, 23:25 UTC | May 21, 00:15 UTC | 50m |
| 2026-05-20 | CGILY | YDT → YDT | May 20, 16:35 UTC | May 20, 17:30 UTC | 55m |
| 2026-05-19 | CGILY | - | May 19, 16:45 UTC | May 19, 17:40 UTC | 55m |
| 2026-05-18 | CGILY | YDT → YDT | May 18, 16:50 UTC | May 18, 17:55 UTC | 1h 5m |
| 2026-05-13 | CGILY | - | May 13, 20:30 UTC | May 13, 21:20 UTC | 50m |
| 2026-05-11 | CGILY | YDT → YDT | May 11, 15:35 UTC | May 11, 16:30 UTC | 55m |
| 2026-05-07 | CGILY | YDT → YDT | May 7, 16:35 UTC | May 7, 17:35 UTC | 1h 0m |
| 2026-05-04 | CGILY | - | May 4, 16:50 UTC | May 4, 17:55 UTC | 1h 5m |
| 2026-04-30 | CGILY | - | Apr 30, 19:00 UTC | Apr 30, 19:45 UTC | 45m |
| 2026-04-29 | CGILY | - | Apr 29, 18:55 UTC | Apr 29, 19:40 UTC | 45m |
| 2026-04-29 | CGILY | YDT → YDT | Apr 29, 16:40 UTC | Apr 29, 17:30 UTC | 50m |
| 2026-04-27 | CGILY | - | Apr 27, 20:45 UTC | Apr 27, 21:35 UTC | 50m |
| 2026-04-27 | CGILY | - | Apr 27, 19:05 UTC | Apr 27, 19:50 UTC | 45m |
| 2026-04-24 | CGILY | - | Apr 24, 20:25 UTC | Apr 24, 21:10 UTC | 45m |
| 2026-04-24 | CGILY | - | Apr 24, 16:35 UTC | Apr 24, 17:35 UTC | 1h 0m |
| 2026-04-22 | CGILY | - | Apr 22, 16:45 UTC | Apr 22, 17:40 UTC | 55m |
| 2026-04-20 | CGILY | - | Apr 20, 23:30 UTC | Apr 21, 00:15 UTC | 45m |
| 2026-04-17 | CGILY | - | Apr 17, 23:45 UTC | Apr 18, 00:30 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-GILY page for operator, model, and routing details .