sensors Mode-S transponder
C00DF9
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FFHO · DE HAVILLAND DHC-2 Beaver · operated by CHARLES TREMBLAY
- Hex
- C00DF9
- Octal
- 60006771
- Decimal
- 12,586,489
- Country
- CA
- Tail
- C-FFHO
- Type
- DHC2
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- Jul 26, 21:25 UTC
Last known position
Country allocation
The ICAO 24-bit address C00DF9 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 |
|---|---|---|---|
| CFFHO | - | 47 | 2026-07-26 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CFFHO | - | Jul 26, 20:45 UTC | Jul 26, 21:25 UTC | 40m |
| 2026-07-25 | CFFHO | - | Jul 25, 12:40 UTC | Jul 25, 13:15 UTC | 35m |
| 2026-07-25 | CFFHO | - | Jul 25, 11:50 UTC | Jul 25, 12:05 UTC | 15m |
| 2026-07-24 | CFFHO | YHU → YMX | Jul 24, 23:40 UTC | Jul 25, 00:45 UTC | 1h 5m |
| 2026-07-24 | CFFHO | - | Jul 24, 21:35 UTC | Jul 24, 21:50 UTC | 15m |
| 2026-07-24 | CFFHO | - | Jul 24, 19:30 UTC | Jul 24, 20:15 UTC | 45m |
| 2026-07-24 | CFFHO | - | Jul 24, 11:40 UTC | Jul 24, 12:35 UTC | 55m |
| 2026-07-23 | CFFHO | - | Jul 23, 21:25 UTC | Jul 23, 22:30 UTC | 1h 5m |
| 2026-07-23 | CFFHO | - | Jul 23, 14:00 UTC | Jul 23, 14:30 UTC | 30m |
| 2026-07-23 | CFFHO | - | Jul 23, 12:55 UTC | Jul 23, 13:05 UTC | 10m |
| 2026-07-21 | CFFHO | YMX → YMX | Jul 21, 13:50 UTC | Jul 21, 15:15 UTC | 1h 25m |
| 2026-07-19 | CFFHO | - | Jul 19, 22:25 UTC | Jul 19, 23:00 UTC | 35m |
| 2026-07-19 | CFFHO | - | Jul 19, 10:55 UTC | Jul 19, 11:35 UTC | 40m |
| 2026-07-17 | CFFHO | - | Jul 17, 17:25 UTC | Jul 17, 18:29 UTC | 1h 5m |
| 2026-07-17 | CFFHO | YMX → YUL | Jul 17, 13:15 UTC | Jul 17, 15:05 UTC | 1h 50m |
| 2026-07-16 | CFFHO | - | Jul 16, 21:25 UTC | Jul 16, 22:35 UTC | 1h 10m |
| 2026-07-16 | CFFHO | - | Jul 16, 16:19 UTC | Jul 16, 17:00 UTC | 40m |
| 2026-07-16 | CFFHO | - | Jul 16, 14:55 UTC | Jul 16, 15:05 UTC | 10m |
| 2026-07-13 | CFFHO | YMX → YMX | Jul 13, 19:05 UTC | Jul 13, 20:25 UTC | 1h 20m |
| 2026-07-10 | CFFHO | - | Jul 10, 19:55 UTC | Jul 10, 20:35 UTC | 40m |
| 2026-07-10 | CFFHO | - | Jul 10, 14:20 UTC | Jul 10, 16:15 UTC | 1h 55m |
| 2026-07-10 | CFFHO | - | Jul 10, 11:30 UTC | Jul 10, 13:40 UTC | 2h 10m |
| 2026-07-03 | CFFHO | - | Jul 3, 19:15 UTC | Jul 3, 21:05 UTC | 1h 50m |
| 2026-06-27 | CFFHO | - | Jun 27, 21:10 UTC | Jun 27, 22:09 UTC | 1h 0m |
| 2026-06-27 | CFFHO | - | Jun 27, 13:00 UTC | Jun 27, 13:30 UTC | 30m |
| 2026-06-27 | CFFHO | - | Jun 27, 11:20 UTC | Jun 27, 11:30 UTC | 10m |
| 2026-06-20 | CFFHO | ZBM → YMX | Jun 20, 19:09 UTC | Jun 20, 20:29 UTC | 1h 20m |
| 2026-06-20 | CFFHO | - | Jun 20, 11:14 UTC | Jun 20, 12:34 UTC | 1h 20m |
| 2026-06-15 | CFFHO | - | Jun 15, 11:49 UTC | Jun 15, 12:35 UTC | 45m |
| 2026-06-13 | CFFHO | - | Jun 13, 19:40 UTC | Jun 13, 20:10 UTC | 30m |
| 2026-06-13 | CFFHO | - | Jun 13, 18:10 UTC | Jun 13, 18:20 UTC | 10m |
| 2026-06-13 | CFFHO | - | Jun 13, 12:05 UTC | Jun 13, 13:20 UTC | 1h 15m |
| 2026-06-12 | CFFHO | - | Jun 12, 15:35 UTC | Jun 12, 17:10 UTC | 1h 35m |
| 2026-05-28 | CFFHO | - | May 28, 22:40 UTC | May 28, 23:25 UTC | 45m |
| 2026-05-28 | CFFHO | - | May 28, 22:00 UTC | May 28, 22:10 UTC | 10m |
| 2026-05-28 | CFFHO | - | May 28, 18:40 UTC | May 28, 19:15 UTC | 35m |
| 2026-05-28 | CFFHO | YMX → YUL | May 28, 17:50 UTC | May 28, 18:05 UTC | 15m |
| 2026-05-22 | CFFHO | - | May 22, 18:05 UTC | May 22, 18:25 UTC | 20m |
| 2026-05-22 | CFFHO | - | May 22, 15:25 UTC | May 22, 16:30 UTC | 1h 5m |
| 2026-05-22 | CFFHO | - | May 22, 12:40 UTC | May 22, 13:05 UTC | 25m |
| 2026-05-22 | CFFHO | YMX → YUL | May 22, 11:50 UTC | May 22, 12:05 UTC | 15m |
| 2026-05-21 | CFFHO | - | May 21, 21:20 UTC | May 21, 21:45 UTC | 25m |
| 2026-05-21 | CFFHO | - | May 21, 20:15 UTC | May 21, 20:25 UTC | 10m |
| 2026-05-21 | CFFHO | - | May 21, 18:45 UTC | May 21, 19:00 UTC | 15m |
| 2026-05-21 | CFFHO | - | May 21, 15:25 UTC | May 21, 17:25 UTC | 2h 0m |
| 2026-04-24 | CFFHO | - | Apr 24, 18:20 UTC | Apr 24, 18:45 UTC | 25m |
| 2026-04-24 | CFFHO | - | Apr 24, 12:15 UTC | Apr 24, 13:55 UTC | 1h 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-FFHO page for operator, model, and routing details .