sensors Mode-S transponder
C03ABC
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FWGH · BEECHCRAFT Super King Air 350
- Hex
- C03ABC
- Octal
- 60035274
- Decimal
- 12,597,948
- Country
- CA
- Tail
- C-FWGH
- Type
- B350
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address C03ABC 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 |
|---|---|---|---|
| AKN867 | - | 50 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AKN867 | - | May 29, 08:10 UTC | May 29, 10:25 UTC | 2h 15m |
| 2026-05-29 | AKN867 | - | May 29, 01:25 UTC | May 29, 05:10 UTC | 3h 45m |
| 2026-05-22 | AKN867 | - | May 22, 08:45 UTC | May 22, 11:45 UTC | 3h 0m |
| 2026-05-22 | AKN867 | - | May 22, 04:50 UTC | May 22, 07:25 UTC | 2h 35m |
| 2026-05-20 | AKN867 | - | May 20, 01:45 UTC | May 20, 05:30 UTC | 3h 46m |
| 2026-05-19 | AKN867 | - | May 19, 21:20 UTC | May 19, 23:45 UTC | 2h 25m |
| 2026-05-17 | AKN867 | - | May 17, 22:15 UTC | May 18, 01:10 UTC | 2h 55m |
| 2026-05-17 | AKN867 | - | May 17, 18:55 UTC | May 17, 20:25 UTC | 1h 30m |
| 2026-05-14 | AKN867 | - | May 14, 23:00 UTC | May 15, 01:40 UTC | 2h 40m |
| 2026-05-14 | AKN867 | - | May 14, 18:00 UTC | May 14, 21:00 UTC | 3h 0m |
| 2026-05-13 | AKN867 | - | May 13, 20:55 UTC | May 13, 23:30 UTC | 2h 35m |
| 2026-05-13 | AKN867 | - | May 13, 18:15 UTC | May 13, 19:05 UTC | 50m |
| 2026-05-13 | AKN867 | - | May 13, 17:25 UTC | May 13, 17:45 UTC | 20m |
| 2026-05-13 | AKN867 | - | May 13, 16:10 UTC | May 13, 16:50 UTC | 40m |
| 2026-05-12 | AKN867 | - | May 12, 06:15 UTC | May 12, 09:00 UTC | 2h 45m |
| 2026-05-12 | AKN867 | - | May 12, 02:45 UTC | May 12, 03:35 UTC | 50m |
| 2026-05-10 | AKN867 | - | May 10, 10:45 UTC | May 10, 13:35 UTC | 2h 50m |
| 2026-05-10 | AKN867 | - | May 10, 05:45 UTC | May 10, 08:54 UTC | 3h 10m |
| 2026-05-09 | AKN867 | - | May 9, 21:30 UTC | May 10, 00:24 UTC | 2h 55m |
| 2026-05-09 | AKN867 | - | May 9, 01:10 UTC | May 9, 19:30 UTC | 18h 20m |
| 2026-05-09 | AKN867 | - | May 9, 00:05 UTC | May 9, 19:30 UTC | 19h 25m |
| 2026-05-08 | AKN867 | - | May 8, 18:55 UTC | May 8, 22:00 UTC | 3h 5m |
| 2026-05-03 | AKN867 | - | May 3, 01:25 UTC | May 3, 04:35 UTC | 3h 9m |
| 2026-05-02 | AKN867 | - | May 2, 21:15 UTC | May 3, 00:01 UTC | 2h 45m |
| 2026-05-02 | AKN867 | - | May 2, 13:35 UTC | May 2, 14:10 UTC | 35m |
| 2026-05-02 | AKN867 | - | May 2, 12:35 UTC | May 2, 13:00 UTC | 25m |
| 2026-05-02 | AKN867 | - | May 2, 11:15 UTC | May 2, 12:00 UTC | 45m |
| 2026-05-02 | AKN867 | - | May 2, 06:45 UTC | May 2, 08:15 UTC | 1h 30m |
| 2026-05-02 | AKN867 | - | May 2, 05:40 UTC | May 2, 06:15 UTC | 35m |
| 2026-04-30 | AKN867 | - | Apr 30, 06:35 UTC | Apr 30, 09:15 UTC | 2h 40m |
| 2026-04-30 | AKN867 | - | Apr 30, 01:05 UTC | Apr 30, 04:00 UTC | 2h 55m |
| 2026-04-29 | AKN867 | - | Apr 29, 06:00 UTC | Apr 29, 09:00 UTC | 3h 1m |
| 2026-04-29 | AKN867 | - | Apr 29, 00:10 UTC | Apr 29, 02:50 UTC | 2h 40m |
| 2026-04-25 | AKN867 | - | Apr 25, 20:30 UTC | Apr 25, 23:40 UTC | 3h 10m |
| 2026-04-25 | AKN867 | - | Apr 25, 15:30 UTC | Apr 25, 18:10 UTC | 2h 40m |
| 2026-04-22 | AKN867 | - | Apr 22, 01:45 UTC | Apr 22, 04:40 UTC | 2h 55m |
| 2026-04-21 | AKN867 | - | Apr 21, 22:05 UTC | Apr 21, 22:50 UTC | 45m |
| 2026-04-21 | AKN867 | - | Apr 21, 21:20 UTC | Apr 21, 21:35 UTC | 15m |
| 2026-04-21 | AKN867 | - | Apr 21, 20:20 UTC | Apr 21, 20:45 UTC | 25m |
| 2026-04-15 | AKN867 | - | Apr 15, 05:25 UTC | Apr 15, 05:55 UTC | 30m |
| 2026-04-15 | AKN867 | - | Apr 15, 03:00 UTC | Apr 15, 04:50 UTC | 1h 50m |
| 2026-04-15 | AKN867 | - | Apr 15, 00:55 UTC | Apr 15, 01:05 UTC | 10m |
| 2026-04-14 | AKN867 | - | Apr 14, 23:25 UTC | Apr 15, 00:50 UTC | 1h 25m |
| 2026-04-14 | AKN867 | - | Apr 14, 22:15 UTC | Apr 14, 22:50 UTC | 35m |
| 2026-04-13 | AKN867 | - | Apr 13, 12:50 UTC | Apr 13, 13:25 UTC | 35m |
| 2026-04-13 | AKN867 | - | Apr 13, 12:00 UTC | Apr 13, 13:25 UTC | 1h 25m |
| 2026-04-13 | AKN867 | - | Apr 13, 10:25 UTC | Apr 13, 12:15 UTC | 1h 50m |
| 2026-04-13 | AKN867 | - | Apr 13, 08:20 UTC | Apr 13, 08:35 UTC | 15m |
| 2026-04-13 | AKN867 | - | Apr 13, 07:55 UTC | Apr 13, 08:35 UTC | 40m |
| 2026-04-13 | AKN867 | - | Apr 13, 05:55 UTC | Apr 13, 08:15 UTC | 2h 20m |
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-FWGH page for operator, model, and routing details .