sensors Mode-S transponder
C05BDB
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GIUK · PIPER PA-28-140/150/160/180 · operated by Abbotsford Flying Club
- Hex
- C05BDB
- Octal
- 60055733
- Decimal
- 12,606,427
- Country
- CA
- Tail
- C-GIUK
- Type
- P28A
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address C05BDB 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 |
|---|---|---|---|
| CGIUK | - | 49 | 2026-06-28 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-28 | CGIUK | YXX → YXX | Jun 28, 00:45 UTC | Jun 28, 01:34 UTC | 50m |
| 2026-06-26 | CGIUK | - | Jun 26, 02:00 UTC | Jun 26, 02:14 UTC | 15m |
| 2026-06-26 | CGIUK | - | Jun 26, 00:39 UTC | Jun 26, 01:05 UTC | 25m |
| 2026-06-23 | CGIUK | - | Jun 23, 19:50 UTC | Jun 23, 20:04 UTC | 15m |
| 2026-06-23 | CGIUK | - | Jun 23, 18:29 UTC | Jun 23, 19:04 UTC | 35m |
| 2026-06-21 | CGIUK | - | Jun 21, 22:10 UTC | Jun 21, 22:40 UTC | 30m |
| 2026-06-21 | CGIUK | - | Jun 21, 19:09 UTC | Jun 21, 19:39 UTC | 30m |
| 2026-06-21 | CGIUK | - | Jun 21, 00:04 UTC | Jun 21, 00:59 UTC | 55m |
| 2026-06-19 | CGIUK | - | Jun 19, 19:14 UTC | Jun 19, 20:29 UTC | 1h 15m |
| 2026-06-12 | CGIUK | - | Jun 12, 18:10 UTC | Jun 12, 19:00 UTC | 50m |
| 2026-06-12 | CGIUK | - | Jun 12, 00:00 UTC | Jun 12, 00:15 UTC | 15m |
| 2026-06-08 | CGIUK | - | Jun 8, 16:20 UTC | Jun 8, 16:30 UTC | 10m |
| 2026-05-31 | CGIUK | YYJ → YXX | May 31, 22:30 UTC | May 31, 23:05 UTC | 35m |
| 2026-05-31 | CGIUK | - | May 31, 19:15 UTC | May 31, 19:45 UTC | 30m |
| 2026-05-30 | CGIUK | - | May 30, 01:00 UTC | May 30, 01:10 UTC | 10m |
| 2026-05-29 | CGIUK | - | May 29, 23:45 UTC | May 30, 00:25 UTC | 40m |
| 2026-05-23 | CGIUK | - | May 23, 22:15 UTC | May 23, 22:40 UTC | 25m |
| 2026-05-23 | CGIUK | - | May 23, 16:10 UTC | May 23, 16:35 UTC | 25m |
| 2026-05-22 | CGIUK | - | May 22, 05:15 UTC | May 22, 06:05 UTC | 50m |
| 2026-05-22 | CGIUK | - | May 22, 03:55 UTC | May 22, 04:35 UTC | 40m |
| 2026-05-19 | CGIUK | - | May 19, 20:00 UTC | May 19, 20:15 UTC | 15m |
| 2026-05-19 | CGIUK | - | May 19, 00:45 UTC | May 19, 01:15 UTC | 30m |
| 2026-05-18 | CGIUK | - | May 18, 22:40 UTC | May 18, 23:35 UTC | 55m |
| 2026-05-18 | CGIUK | - | May 18, 18:20 UTC | May 18, 18:50 UTC | 29m |
| 2026-05-18 | CGIUK | - | May 18, 04:51 UTC | May 18, 05:45 UTC | 55m |
| 2026-05-18 | CGIUK | - | May 18, 00:25 UTC | May 18, 01:20 UTC | 55m |
| 2026-05-17 | CGIUK | - | May 17, 18:30 UTC | May 17, 18:40 UTC | 10m |
| 2026-05-17 | CGIUK | - | May 17, 16:35 UTC | May 17, 16:45 UTC | 10m |
| 2026-05-14 | CGIUK | YXX → YXX | May 14, 05:00 UTC | May 14, 05:10 UTC | 10m |
| 2026-05-10 | CGIUK | - | May 10, 14:54 UTC | May 10, 15:39 UTC | 45m |
| 2026-05-09 | CGIUK | XQU → YXX | May 9, 20:05 UTC | May 9, 21:00 UTC | 55m |
| 2026-05-09 | CGIUK | - | May 9, 17:20 UTC | May 9, 18:20 UTC | 1h 0m |
| 2026-05-06 | CGIUK | - | May 6, 00:46 UTC | May 6, 01:05 UTC | 20m |
| 2026-05-05 | CGIUK | - | May 5, 23:20 UTC | May 6, 00:10 UTC | 50m |
| 2026-05-05 | CGIUK | - | May 5, 17:10 UTC | May 5, 18:40 UTC | 1h 30m |
| 2026-04-26 | CGIUK | - | Apr 26, 19:55 UTC | Apr 26, 20:25 UTC | 30m |
| 2026-04-26 | CGIUK | - | Apr 26, 17:10 UTC | Apr 26, 17:35 UTC | 25m |
| 2026-04-26 | CGIUK | - | Apr 26, 00:15 UTC | Apr 26, 01:00 UTC | 45m |
| 2026-04-25 | CGIUK | - | Apr 25, 20:35 UTC | Apr 25, 21:25 UTC | 50m |
| 2026-04-25 | CGIUK | - | Apr 25, 18:05 UTC | Apr 25, 19:00 UTC | 55m |
| 2026-04-20 | CGIUK | - | Apr 20, 02:50 UTC | Apr 20, 03:50 UTC | 1h 0m |
| 2026-04-19 | CGIUK | - | Apr 19, 22:10 UTC | Apr 19, 22:35 UTC | 25m |
| 2026-04-19 | CGIUK | - | Apr 19, 19:15 UTC | Apr 19, 19:25 UTC | 10m |
| 2026-04-19 | CGIUK | - | Apr 19, 16:45 UTC | Apr 19, 16:55 UTC | 10m |
| 2026-04-19 | CGIUK | - | Apr 19, 14:55 UTC | Apr 19, 15:35 UTC | 40m |
| 2026-04-19 | CGIUK | - | Apr 19, 02:30 UTC | Apr 19, 03:15 UTC | 45m |
| 2026-04-18 | CGIUK | - | Apr 18, 23:45 UTC | Apr 19, 00:45 UTC | 1h 0m |
| 2026-04-15 | CGIUK | - | Apr 15, 19:05 UTC | Apr 15, 19:25 UTC | 20m |
| 2026-04-15 | CGIUK | - | Apr 15, 18:15 UTC | Apr 15, 18:30 UTC | 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-GIUK page for operator, model, and routing details .