sensors Mode-S transponder
C00D42
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FFAN · BEECHCRAFT Super King Air 350 · operated by The North West Company Limited Partnership, by it's General Partner, NWC GP Inc.
- Hex
- C00D42
- Octal
- 60006502
- Decimal
- 12,586,306
- Country
- CA
- Tail
- C-FFAN
- Type
- B350
- Flights observed
- 83
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address C00D42 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 |
|---|---|---|---|
| CFFAN | - | 83 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CFFAN | YWG → YWG | Jul 17, 12:45 UTC | Jul 17, 22:15 UTC | 9h 30m |
| 2026-07-16 | CFFAN | YWG → YWG | Jul 16, 13:00 UTC | Jul 17, 00:14 UTC | 11h 15m |
| 2026-07-15 | CFFAN | YWG → YWG | Jul 15, 12:50 UTC | Jul 16, 00:45 UTC | 11h 55m |
| 2026-07-14 | CFFAN | - | Jul 14, 21:40 UTC | Jul 14, 22:15 UTC | 35m |
| 2026-07-13 | CFFAN | - | Jul 13, 13:30 UTC | Jul 13, 15:50 UTC | 2h 20m |
| 2026-07-10 | CFFAN | - | Jul 10, 19:25 UTC | Jul 10, 20:10 UTC | 45m |
| 2026-07-10 | CFFAN | - | Jul 10, 13:05 UTC | Jul 10, 13:35 UTC | 30m |
| 2026-07-09 | CFFAN | YWG → YWG | Jul 9, 13:10 UTC | Jul 9, 20:00 UTC | 6h 50m |
| 2026-07-08 | CFFAN | YWG → YWG | Jul 8, 13:00 UTC | Jul 8, 22:05 UTC | 9h 5m |
| 2026-07-07 | CFFAN | - | Jul 7, 16:20 UTC | Jul 7, 17:05 UTC | 45m |
| 2026-07-06 | CFFAN | - | Jul 6, 13:35 UTC | Jul 6, 14:10 UTC | 35m |
| 2026-07-04 | CFFAN | - | Jul 4, 20:45 UTC | Jul 4, 21:15 UTC | 30m |
| 2026-06-26 | CFFAN | - | Jun 26, 21:04 UTC | Jun 26, 21:39 UTC | 35m |
| 2026-06-26 | CFFAN | - | Jun 26, 19:35 UTC | Jun 26, 20:20 UTC | 45m |
| 2026-06-25 | CFFAN | - | Jun 25, 21:35 UTC | Jun 26, 20:20 UTC | 22h 45m |
| 2026-06-22 | CFFAN | - | Jun 22, 12:19 UTC | Jun 22, 15:45 UTC | 3h 25m |
| 2026-06-19 | CFFAN | - | Jun 19, 19:39 UTC | Jun 19, 20:19 UTC | 40m |
| 2026-06-19 | CFFAN | - | Jun 19, 12:49 UTC | Jun 19, 13:20 UTC | 30m |
| 2026-06-18 | CFFAN | - | Jun 18, 21:10 UTC | Jun 18, 21:45 UTC | 35m |
| 2026-06-18 | CFFAN | - | Jun 18, 12:50 UTC | Jun 18, 13:30 UTC | 40m |
| 2026-06-17 | CFFAN | - | Jun 17, 20:45 UTC | Jun 17, 21:30 UTC | 45m |
| 2026-06-17 | CFFAN | - | Jun 17, 12:50 UTC | Jun 17, 13:35 UTC | 45m |
| 2026-06-16 | CFFAN | - | Jun 16, 21:10 UTC | Jun 16, 21:50 UTC | 40m |
| 2026-06-16 | CFFAN | - | Jun 16, 12:50 UTC | Jun 16, 13:40 UTC | 50m |
| 2026-06-15 | CFFAN | - | Jun 15, 21:09 UTC | Jun 15, 21:45 UTC | 35m |
| 2026-06-15 | CFFAN | - | Jun 15, 13:10 UTC | Jun 15, 14:00 UTC | 50m |
| 2026-06-12 | CFFAN | - | Jun 12, 20:55 UTC | Jun 12, 21:40 UTC | 45m |
| 2026-06-12 | CFFAN | - | Jun 12, 12:55 UTC | Jun 12, 13:45 UTC | 50m |
| 2026-06-11 | CFFAN | YWG → YWG | Jun 11, 12:55 UTC | Jun 11, 22:00 UTC | 9h 5m |
| 2026-06-10 | CFFAN | YWG → YWG | Jun 10, 17:00 UTC | Jun 10, 22:30 UTC | 5h 30m |
| 2026-06-10 | CFFAN | - | Jun 10, 13:20 UTC | Jun 10, 13:40 UTC | 20m |
| 2026-06-09 | CFFAN | - | Jun 9, 13:00 UTC | Jun 9, 22:50 UTC | 9h 50m |
| 2026-06-08 | CFFAN | - | Jun 8, 21:40 UTC | Jun 8, 22:40 UTC | 1h 0m |
| 2026-06-08 | CFFAN | - | Jun 8, 13:05 UTC | Jun 8, 13:35 UTC | 30m |
| 2026-06-06 | CFFAN | - | Jun 6, 00:10 UTC | Jun 6, 00:55 UTC | 45m |
| 2026-06-05 | CFFAN | - | Jun 5, 18:20 UTC | Jun 5, 19:10 UTC | 50m |
| 2026-06-04 | CFFAN | - | Jun 4, 22:05 UTC | Jun 4, 22:25 UTC | 20m |
| 2026-06-04 | CFFAN | - | Jun 4, 21:45 UTC | Jun 4, 22:00 UTC | 15m |
| 2026-06-04 | CFFAN | - | Jun 4, 20:40 UTC | Jun 4, 21:40 UTC | 1h 0m |
| 2026-06-04 | CFFAN | - | Jun 4, 18:05 UTC | Jun 4, 18:25 UTC | 20m |
| 2026-06-04 | CFFAN | - | Jun 4, 17:45 UTC | Jun 4, 18:00 UTC | 15m |
| 2026-06-04 | CFFAN | - | Jun 4, 16:45 UTC | Jun 4, 17:40 UTC | 55m |
| 2026-06-02 | CFFAN | - | Jun 2, 18:20 UTC | Jun 2, 19:10 UTC | 50m |
| 2026-06-01 | CFFAN | - | Jun 1, 20:50 UTC | Jun 2, 19:10 UTC | 22h 20m |
| 2026-06-01 | CFFAN | - | Jun 1, 15:35 UTC | Jun 1, 16:20 UTC | 45m |
| 2026-05-30 | CFFAN | YWG → YWG | May 30, 12:45 UTC | May 30, 20:05 UTC | 7h 20m |
| 2026-05-29 | CFFAN | - | May 29, 23:40 UTC | May 30, 00:25 UTC | 45m |
| 2026-05-29 | CFFAN | - | May 29, 19:00 UTC | May 29, 19:15 UTC | 15m |
| 2026-05-29 | CFFAN | - | May 29, 16:55 UTC | May 29, 18:20 UTC | 1h 25m |
| 2026-05-28 | CFFAN | - | May 28, 21:55 UTC | May 28, 22:35 UTC | 40m |
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-FFAN page for operator, model, and routing details .