sensors Mode-S transponder
C01823
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FJDQ · BEECH 100 King Air · operated by Max Aviation inc.
- Hex
- C01823
- Octal
- 60014043
- Decimal
- 12,589,091
- Country
- CA
- Tail
- C-FJDQ
- Type
- BE10
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address C01823 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 |
|---|---|---|---|
| CFJDQ | - | 48 | 2026-05-26 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | CFJDQ | - | May 26, 12:45 UTC | May 26, 13:34 UTC | 50m |
| 2026-05-26 | CFJDQ | - | May 26, 11:05 UTC | May 26, 11:50 UTC | 45m |
| 2026-05-25 | CFJDQ | - | May 25, 21:24 UTC | May 25, 22:15 UTC | 50m |
| 2026-05-25 | CFJDQ | - | May 25, 12:45 UTC | May 25, 13:35 UTC | 50m |
| 2026-05-25 | CFJDQ | - | May 25, 11:20 UTC | May 25, 11:35 UTC | 15m |
| 2026-05-24 | CFJDQ | - | May 24, 17:10 UTC | May 24, 17:30 UTC | 20m |
| 2026-05-24 | CFJDQ | YHU → YQB | May 24, 14:45 UTC | May 24, 15:25 UTC | 40m |
| 2026-05-20 | CFJDQ | YHU → YHU | May 20, 16:25 UTC | May 20, 18:20 UTC | 1h 55m |
| 2026-05-20 | CFJDQ | - | May 20, 12:35 UTC | May 20, 14:25 UTC | 1h 50m |
| 2026-05-19 | CFJDQ | - | May 19, 18:40 UTC | May 19, 19:30 UTC | 50m |
| 2026-05-19 | CFJDQ | - | May 19, 10:50 UTC | May 19, 11:30 UTC | 40m |
| 2026-05-14 | CFJDQ | - | May 14, 22:25 UTC | May 14, 23:20 UTC | 55m |
| 2026-05-14 | CFJDQ | - | May 14, 20:45 UTC | May 14, 21:20 UTC | 35m |
| 2026-05-14 | CFJDQ | - | May 14, 15:20 UTC | May 14, 16:10 UTC | 50m |
| 2026-05-13 | CFJDQ | - | May 13, 17:10 UTC | May 13, 17:30 UTC | 20m |
| 2026-05-12 | CFJDQ | - | May 12, 11:20 UTC | May 12, 11:30 UTC | 10m |
| 2026-05-11 | CFJDQ | - | May 11, 17:40 UTC | May 11, 18:35 UTC | 55m |
| 2026-05-11 | CFJDQ | - | May 11, 12:45 UTC | May 11, 13:15 UTC | 30m |
| 2026-05-08 | CFJDQ | YHU → YHU | May 8, 12:39 UTC | May 8, 14:25 UTC | 1h 45m |
| 2026-05-07 | CFJDQ | - | May 7, 12:55 UTC | May 7, 13:45 UTC | 50m |
| 2026-05-07 | CFJDQ | - | May 7, 11:00 UTC | May 7, 11:40 UTC | 40m |
| 2026-05-06 | CFJDQ | - | May 6, 17:05 UTC | May 6, 18:15 UTC | 1h 9m |
| 2026-05-05 | CFJDQ | - | May 5, 12:25 UTC | May 5, 12:35 UTC | 10m |
| 2026-05-05 | CFJDQ | - | May 5, 11:20 UTC | May 5, 11:55 UTC | 35m |
| 2026-05-04 | CFJDQ | YYZ → YHU | May 4, 17:40 UTC | May 4, 18:50 UTC | 1h 11m |
| 2026-05-04 | CFJDQ | - | May 4, 15:20 UTC | May 4, 16:35 UTC | 1h 15m |
| 2026-05-04 | CFJDQ | - | May 4, 11:40 UTC | May 4, 12:20 UTC | 40m |
| 2026-04-30 | CFJDQ | - | Apr 30, 22:40 UTC | Apr 30, 23:25 UTC | 45m |
| 2026-04-30 | CFJDQ | - | Apr 30, 20:50 UTC | Apr 30, 21:30 UTC | 40m |
| 2026-04-30 | CFJDQ | YHU → YHU | Apr 30, 15:50 UTC | Apr 30, 17:15 UTC | 1h 25m |
| 2026-04-30 | CFJDQ | - | Apr 30, 12:40 UTC | Apr 30, 13:30 UTC | 50m |
| 2026-04-30 | CFJDQ | - | Apr 30, 10:50 UTC | Apr 30, 11:30 UTC | 40m |
| 2026-04-29 | CFJDQ | YHU → YHU | Apr 29, 14:45 UTC | Apr 29, 16:00 UTC | 1h 15m |
| 2026-04-28 | CFJDQ | YHU → YHU | Apr 28, 16:50 UTC | Apr 28, 18:10 UTC | 1h 20m |
| 2026-04-28 | CFJDQ | - | Apr 28, 12:30 UTC | Apr 28, 14:20 UTC | 1h 50m |
| 2026-04-24 | CFJDQ | YHU → YHU | Apr 24, 17:05 UTC | Apr 24, 18:55 UTC | 1h 50m |
| 2026-04-23 | CFJDQ | - | Apr 23, 22:35 UTC | Apr 23, 23:25 UTC | 50m |
| 2026-04-23 | CFJDQ | - | Apr 23, 20:45 UTC | Apr 23, 21:35 UTC | 50m |
| 2026-04-23 | CFJDQ | - | Apr 23, 12:50 UTC | Apr 23, 13:35 UTC | 45m |
| 2026-04-23 | CFJDQ | - | Apr 23, 11:01 UTC | Apr 23, 11:45 UTC | 45m |
| 2026-04-21 | CFJDQ | - | Apr 21, 22:45 UTC | Apr 21, 23:25 UTC | 40m |
| 2026-04-21 | CFJDQ | - | Apr 21, 21:05 UTC | Apr 21, 21:45 UTC | 40m |
| 2026-04-21 | CFJDQ | - | Apr 21, 12:45 UTC | Apr 21, 13:30 UTC | 45m |
| 2026-04-21 | CFJDQ | - | Apr 21, 11:05 UTC | Apr 21, 11:50 UTC | 45m |
| 2026-04-16 | CFJDQ | - | Apr 16, 19:40 UTC | Apr 16, 20:40 UTC | 1h 0m |
| 2026-04-14 | CFJDQ | - | Apr 14, 13:30 UTC | Apr 14, 14:30 UTC | 1h 0m |
| 2026-04-14 | CFJDQ | - | Apr 14, 12:50 UTC | Apr 14, 13:00 UTC | 10m |
| 2026-04-13 | CFJDQ | YHU → YHU | Apr 13, 13:55 UTC | Apr 13, 15:40 UTC | 1h 45m |
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-FJDQ page for operator, model, and routing details .