sensors Mode-S transponder
C001D8
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FASD · BOMBARDIER BD-700 Global 6000/6500 · operated by The Futura Corporation
- Hex
- C001D8
- Octal
- 60000730
- Decimal
- 12,583,384
- Country
- CA
- Tail
- C-FASD
- Type
- GLEX
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address C001D8 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 |
|---|---|---|---|
| CFASD | - | 55 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CFASD | MCC → VNY | Jul 17, 22:40 UTC | Jul 17, 23:35 UTC | 55m |
| 2026-07-17 | CFASD | SJC → MCC | Jul 17, 18:44 UTC | Jul 17, 19:15 UTC | 30m |
| 2026-07-17 | CFASD | - | Jul 17, 15:49 UTC | Jul 17, 17:50 UTC | 2h 0m |
| 2026-07-17 | CFASD | - | Jul 17, 14:44 UTC | Jul 17, 15:00 UTC | 15m |
| 2026-07-15 | CFASD | - | Jul 15, 16:35 UTC | Jul 15, 17:20 UTC | 45m |
| 2026-07-13 | CFASD | - | Jul 13, 00:35 UTC | Jul 13, 00:55 UTC | 20m |
| 2026-07-12 | CFASD | - | Jul 12, 16:45 UTC | Jul 12, 16:55 UTC | 10m |
| 2026-07-08 | CFASD | - | Jul 8, 13:30 UTC | Jul 8, 17:20 UTC | 3h 50m |
| 2026-07-07 | CFASD | - | Jul 7, 15:00 UTC | Jul 7, 18:30 UTC | 3h 30m |
| 2026-07-05 | CFASD | - | Jul 5, 03:25 UTC | Jul 5, 04:05 UTC | 40m |
| 2026-07-04 | CFASD | - | Jul 4, 20:55 UTC | Jul 4, 21:25 UTC | 30m |
| 2026-06-28 | CFASD | - | Jun 28, 03:00 UTC | Jun 28, 03:35 UTC | 35m |
| 2026-06-27 | CFASD | - | Jun 27, 21:04 UTC | Jun 27, 21:40 UTC | 35m |
| 2026-06-23 | CFASD | - | Jun 23, 19:55 UTC | Jun 23, 23:55 UTC | 4h 0m |
| 2026-06-23 | CFASD | - | Jun 23, 18:25 UTC | Jun 23, 19:00 UTC | 35m |
| 2026-06-21 | CFASD | AUS → ADS | Jun 21, 18:50 UTC | Jun 21, 19:34 UTC | 45m |
| 2026-06-20 | CFASD | HSH → AUS | Jun 20, 20:14 UTC | Jun 20, 22:25 UTC | 2h 10m |
| 2026-06-19 | CFASD | - | Jun 19, 17:49 UTC | Jun 19, 19:49 UTC | 2h 0m |
| 2026-06-19 | CFASD | - | Jun 19, 16:55 UTC | Jun 19, 17:24 UTC | 30m |
| 2026-06-14 | CFASD | - | Jun 14, 02:55 UTC | Jun 14, 04:35 UTC | 1h 40m |
| 2026-06-13 | CFASD | - | Jun 13, 20:05 UTC | Jun 13, 21:35 UTC | 1h 30m |
| 2026-06-11 | CFASD | - | Jun 11, 19:40 UTC | Jun 11, 23:45 UTC | 4h 5m |
| 2026-06-11 | CFASD | - | Jun 11, 16:00 UTC | Jun 11, 16:25 UTC | 25m |
| 2026-06-10 | CFASD | - | Jun 10, 14:00 UTC | Jun 10, 17:15 UTC | 3h 15m |
| 2026-06-03 | CFASD | - | Jun 3, 20:10 UTC | Jun 3, 20:55 UTC | 45m |
| 2026-06-03 | CFASD | - | Jun 3, 15:05 UTC | Jun 3, 15:40 UTC | 35m |
| 2026-05-27 | CFASD | - | May 27, 13:10 UTC | May 27, 16:45 UTC | 3h 35m |
| 2026-05-26 | CFASD | - | May 26, 19:40 UTC | May 26, 21:14 UTC | 1h 35m |
| 2026-05-25 | CFASD | YVR → YYZ | May 25, 17:20 UTC | May 25, 21:15 UTC | 3h 54m |
| 2026-05-23 | CFASD | - | May 23, 02:00 UTC | May 23, 03:05 UTC | 1h 5m |
| 2026-05-23 | CFASD | - | May 23, 00:10 UTC | May 23, 00:45 UTC | 35m |
| 2026-05-22 | CFASD | - | May 22, 16:45 UTC | May 22, 17:50 UTC | 1h 5m |
| 2026-05-18 | CFASD | PHX → YVR | May 18, 21:05 UTC | May 18, 23:35 UTC | 2h 30m |
| 2026-05-15 | CFASD | - | May 15, 19:50 UTC | May 15, 22:20 UTC | 2h 30m |
| 2026-05-05 | CFASD | YYZ → YVR | May 5, 16:00 UTC | May 5, 20:10 UTC | 4h 10m |
| 2026-05-04 | CFASD | - | May 4, 18:20 UTC | May 4, 22:10 UTC | 3h 51m |
| 2026-05-01 | CFASD | MCC → YVR | May 1, 18:35 UTC | May 1, 20:05 UTC | 1h 30m |
| 2026-05-01 | CFASD | - | May 1, 16:50 UTC | May 1, 17:10 UTC | 20m |
| 2026-04-29 | CFASD | - | Apr 29, 20:00 UTC | Apr 29, 21:15 UTC | 1h 15m |
| 2026-04-29 | CFASD | - | Apr 29, 19:00 UTC | Apr 29, 19:35 UTC | 35m |
| 2026-04-22 | CFASD | - | Apr 22, 21:25 UTC | Apr 23, 01:05 UTC | 3h 40m |
| 2026-04-22 | CFASD | - | Apr 22, 16:35 UTC | Apr 22, 18:15 UTC | 1h 40m |
| 2026-04-21 | CFASD | - | Apr 21, 20:35 UTC | Apr 21, 21:10 UTC | 35m |
| 2026-04-21 | CFASD | - | Apr 21, 15:31 UTC | Apr 21, 18:45 UTC | 3h 15m |
| 2026-04-17 | CFASD | - | Apr 17, 01:20 UTC | Apr 17, 01:45 UTC | 25m |
| 2026-04-16 | CFASD | - | Apr 16, 23:20 UTC | Apr 17, 01:15 UTC | 1h 55m |
| 2026-04-16 | CFASD | - | Apr 16, 21:14 UTC | Apr 16, 23:10 UTC | 1h 55m |
| 2026-04-16 | CFASD | - | Apr 16, 20:05 UTC | Apr 16, 21:10 UTC | 1h 5m |
| 2026-04-16 | CFASD | - | Apr 16, 17:15 UTC | Apr 16, 19:10 UTC | 1h 55m |
| 2026-04-16 | CFASD | - | Apr 16, 17:05 UTC | Apr 16, 17:10 UTC | 5m |
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-FASD page for operator, model, and routing details .