sensors Mode-S transponder
C01D5E
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FLDD · BOMBARDIER BD-100 Challenger 300 · operated by LID Brokerage & Realty Co. (1977) Ltd.
- Hex
- C01D5E
- Octal
- 60016536
- Decimal
- 12,590,430
- Country
- CA
- Tail
- C-FLDD
- Type
- CL30
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C01D5E 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 |
|---|---|---|---|
| CFLDD | - | 52 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-15 | CFLDD | - | Jun 15, 16:40 UTC | Jun 15, 17:54 UTC | 1h 15m |
| 2026-06-15 | CFLDD | - | Jun 15, 15:55 UTC | Jun 15, 16:09 UTC | 15m |
| 2026-06-15 | CFLDD | - | Jun 15, 14:40 UTC | Jun 15, 15:25 UTC | 45m |
| 2026-06-15 | CFLDD | YYC → YXE | Jun 15, 12:55 UTC | Jun 15, 13:45 UTC | 50m |
| 2026-06-12 | CFLDD | - | Jun 12, 16:00 UTC | Jun 12, 19:20 UTC | 3h 20m |
| 2026-06-10 | CFLDD | - | Jun 10, 17:55 UTC | Jun 10, 20:10 UTC | 2h 15m |
| 2026-06-10 | CFLDD | - | Jun 10, 15:55 UTC | Jun 10, 16:35 UTC | 40m |
| 2026-05-30 | CFLDD | - | May 30, 02:20 UTC | May 30, 03:15 UTC | 55m |
| 2026-05-29 | CFLDD | SJC → YXE | May 29, 23:15 UTC | May 30, 01:50 UTC | 2h 35m |
| 2026-05-29 | CFLDD | - | May 29, 20:25 UTC | May 29, 20:40 UTC | 15m |
| 2026-05-26 | CFLDD | - | May 26, 15:49 UTC | May 26, 17:44 UTC | 1h 55m |
| 2026-05-26 | CFLDD | - | May 26, 14:20 UTC | May 26, 15:09 UTC | 50m |
| 2026-05-26 | CFLDD | - | May 26, 13:00 UTC | May 26, 13:50 UTC | 50m |
| 2026-05-25 | CFLDD | - | May 25, 04:30 UTC | May 25, 04:50 UTC | 20m |
| 2026-05-25 | CFLDD | - | May 25, 03:00 UTC | May 25, 03:50 UTC | 50m |
| 2026-05-24 | CFLDD | - | May 24, 23:10 UTC | May 25, 02:25 UTC | 3h 15m |
| 2026-05-21 | CFLDD | YXE → YHU | May 21, 16:50 UTC | May 21, 19:50 UTC | 3h 0m |
| 2026-05-21 | CFLDD | - | May 21, 15:10 UTC | May 21, 16:05 UTC | 55m |
| 2026-05-21 | CFLDD | - | May 21, 14:20 UTC | May 21, 14:35 UTC | 15m |
| 2026-05-20 | CFLDD | - | May 20, 02:30 UTC | May 20, 03:25 UTC | 55m |
| 2026-05-19 | CFLDD | - | May 19, 23:20 UTC | May 20, 02:05 UTC | 2h 45m |
| 2026-05-16 | CFLDD | - | May 16, 17:10 UTC | May 16, 18:25 UTC | 1h 15m |
| 2026-05-16 | CFLDD | - | May 16, 14:41 UTC | May 16, 16:25 UTC | 1h 45m |
| 2026-05-16 | CFLDD | YYC → YXE | May 16, 13:11 UTC | May 16, 13:55 UTC | 45m |
| 2026-05-04 | CFLDD | - | May 4, 00:45 UTC | May 4, 01:44 UTC | 1h 0m |
| 2026-05-03 | CFLDD | - | May 3, 19:25 UTC | May 4, 00:15 UTC | 4h 50m |
| 2026-05-02 | CFLDD | HWO → FLL | May 2, 16:30 UTC | May 2, 16:40 UTC | 10m |
| 2026-05-01 | CFLDD | IAD → OPF | May 1, 03:55 UTC | May 1, 05:55 UTC | 2h 0m |
| 2026-05-01 | CFLDD | - | May 1, 01:55 UTC | May 1, 02:55 UTC | 1h 0m |
| 2026-04-27 | CFLDD | - | Apr 27, 17:10 UTC | Apr 27, 19:55 UTC | 2h 45m |
| 2026-04-27 | CFLDD | YYC → YXE | Apr 27, 16:05 UTC | Apr 27, 16:50 UTC | 45m |
| 2026-04-26 | CFLDD | - | Apr 26, 00:10 UTC | Apr 26, 01:00 UTC | 50m |
| 2026-04-25 | CFLDD | - | Apr 25, 21:05 UTC | Apr 26, 00:00 UTC | 2h 55m |
| 2026-04-25 | CFLDD | - | Apr 25, 00:00 UTC | Apr 25, 02:45 UTC | 2h 45m |
| 2026-04-24 | CFLDD | YYC → YXE | Apr 24, 22:50 UTC | Apr 24, 23:40 UTC | 50m |
| 2026-04-23 | CFLDD | - | Apr 23, 02:10 UTC | Apr 23, 03:00 UTC | 50m |
| 2026-04-22 | CFLDD | SJC → YXE | Apr 22, 23:10 UTC | Apr 23, 01:45 UTC | 2h 35m |
| 2026-04-22 | CFLDD | - | Apr 22, 21:00 UTC | Apr 22, 21:20 UTC | 20m |
| 2026-04-20 | CFLDD | - | Apr 20, 04:45 UTC | Apr 20, 05:10 UTC | 25m |
| 2026-04-20 | CFLDD | YXE → SFO | Apr 20, 01:10 UTC | Apr 20, 04:10 UTC | 3h 0m |
| 2026-04-19 | CFLDD | - | Apr 19, 15:10 UTC | Apr 19, 17:40 UTC | 2h 30m |
| 2026-04-16 | CFLDD | - | Apr 16, 19:15 UTC | Apr 16, 19:35 UTC | 20m |
| 2026-04-16 | CFLDD | - | Apr 16, 18:20 UTC | Apr 16, 19:10 UTC | 50m |
| 2026-04-16 | CFLDD | - | Apr 16, 17:15 UTC | Apr 16, 17:50 UTC | 35m |
| 2026-04-16 | CFLDD | - | Apr 16, 16:05 UTC | Apr 16, 17:10 UTC | 1h 5m |
| 2026-04-16 | CFLDD | - | Apr 16, 15:15 UTC | Apr 16, 15:35 UTC | 20m |
| 2026-04-16 | CFLDD | - | Apr 16, 14:45 UTC | Apr 16, 15:10 UTC | 25m |
| 2026-04-16 | CFLDD | - | Apr 16, 01:10 UTC | Apr 16, 02:00 UTC | 50m |
| 2026-04-15 | CFLDD | - | Apr 15, 23:10 UTC | Apr 16, 01:05 UTC | 1h 55m |
| 2026-04-15 | CFLDD | - | Apr 15, 22:05 UTC | Apr 15, 23:00 UTC | 55m |
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-FLDD page for operator, model, and routing details .