sensors Mode-S transponder
C01FD9
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FMBO · ROBINSON R-44 Raven · operated by KEEWATIN AIR LP AS REPRESENTED BY ITS GENERAL PARTNER, KEEWATIN AIR GP INC. (KIVALLIQ AIR NUNAVUT LIFELINE)
- Hex
- C01FD9
- Octal
- 60017731
- Decimal
- 12,591,065
- Country
- CA
- Tail
- C-FMBO
- Type
- R44
- Flights observed
- 71
- Distinct callsigns
- 2
- Country
- CA
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address C01FD9 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | CFMBO | - | Jul 23, 22:15 UTC | Jul 23, 23:15 UTC | 1h 0m |
| 2026-07-23 | CFMBO | - | Jul 23, 18:40 UTC | Jul 23, 21:15 UTC | 2h 35m |
| 2026-07-23 | CFMBO | - | Jul 23, 12:20 UTC | Jul 23, 15:00 UTC | 2h 40m |
| 2026-07-23 | CFMBO | - | Jul 23, 04:25 UTC | Jul 23, 04:55 UTC | 30m |
| 2026-07-23 | CFMBO | - | Jul 23, 02:45 UTC | Jul 23, 03:15 UTC | 30m |
| 2026-07-20 | CFMBO | - | Jul 20, 18:40 UTC | Jul 20, 20:40 UTC | 2h 0m |
| 2026-07-20 | CFMBO | - | Jul 20, 14:00 UTC | Jul 20, 15:50 UTC | 1h 50m |
| 2026-07-19 | CFMBO | YWG → YWG | Jul 19, 03:45 UTC | Jul 19, 07:35 UTC | 3h 50m |
| 2026-07-18 | CFMBO | YWG → YWG | Jul 18, 01:15 UTC | Jul 18, 05:25 UTC | 4h 11m |
| 2026-07-15 | CFMBO | YWG → YWG | Jul 15, 01:45 UTC | Jul 15, 05:25 UTC | 3h 40m |
| 2026-07-10 | CFMBO | YWG → YWG | Jul 10, 21:20 UTC | Jul 11, 01:45 UTC | 4h 25m |
| 2026-07-09 | CFMBO | YTZ → YWG | Jul 9, 18:45 UTC | Jul 9, 21:20 UTC | 2h 35m |
| 2026-07-09 | CFMBO | YWG → YTZ | Jul 9, 14:05 UTC | Jul 9, 16:15 UTC | 2h 10m |
| 2026-07-07 | CFMBO | - | Jul 7, 18:55 UTC | Jul 7, 20:35 UTC | 1h 40m |
| 2026-07-07 | CFMBO | YWG → YEG | Jul 7, 14:05 UTC | Jul 7, 16:05 UTC | 2h 0m |
| 2026-07-05 | CFMBO | - | Jul 5, 19:50 UTC | Jul 5, 21:25 UTC | 1h 35m |
| 2026-07-05 | CFMBO | - | Jul 5, 15:05 UTC | Jul 5, 17:00 UTC | 1h 55m |
| 2026-07-03 | CFMBO | YWG → YWG | Jul 3, 02:25 UTC | Jul 3, 05:35 UTC | 3h 10m |
| 2026-07-01 | CFMBO | - | Jul 1, 17:05 UTC | Jul 1, 18:50 UTC | 1h 45m |
| 2026-07-01 | CFMBO | YWG → YEG | Jul 1, 14:20 UTC | Jul 1, 16:05 UTC | 1h 45m |
| 2026-07-01 | CFMBO | YYZ → YWG | Jul 1, 06:15 UTC | Jul 1, 08:40 UTC | 2h 25m |
| 2026-07-01 | CFMBO | YWG → YYZ | Jul 1, 02:00 UTC | Jul 1, 04:00 UTC | 2h 0m |
| 2026-06-30 | CFMBO | - | Jun 30, 20:40 UTC | Jun 30, 21:15 UTC | 35m |
| 2026-06-30 | CFMBO | - | Jun 30, 17:15 UTC | Jun 30, 17:50 UTC | 35m |
| 2026-06-30 | CFMBO | YWG → YWG | Jun 30, 05:35 UTC | Jun 30, 09:40 UTC | 4h 5m |
| 2026-06-29 | CFMBO | - | Jun 29, 22:59 UTC | Jun 29, 23:05 UTC | 5m |
| 2026-06-29 | CFMBO | - | Jun 29, 22:39 UTC | Jun 29, 22:49 UTC | 10m |
| 2026-06-28 | CFMBO | - | Jun 28, 18:55 UTC | Jun 28, 20:45 UTC | 1h 50m |
| 2026-06-28 | CFMBO | - | Jun 28, 14:59 UTC | Jun 28, 16:39 UTC | 1h 40m |
| 2026-06-22 | CFMBO | YWG → YWG | Jun 22, 13:39 UTC | Jun 22, 19:29 UTC | 5h 50m |
| 2026-06-19 | CFMBO | YWG → YWG | Jun 19, 08:20 UTC | Jun 19, 13:44 UTC | 5h 25m |
| 2026-06-18 | CFMBO | - | Jun 18, 18:35 UTC | Jun 18, 20:05 UTC | 1h 30m |
| 2026-06-18 | CFMBO | - | Jun 18, 13:55 UTC | Jun 18, 15:40 UTC | 1h 45m |
| 2026-06-13 | CFMBO | YWG → YWG | Jun 13, 01:35 UTC | Jun 13, 01:55 UTC | 20m |
| 2026-06-04 | CFMBO | YWG → YWG | Jun 4, 21:40 UTC | Jun 4, 22:10 UTC | 30m |
| 2026-05-31 | CFMBO | - | May 31, 21:20 UTC | May 31, 23:10 UTC | 1h 50m |
| 2026-05-31 | CFMBO | - | May 31, 17:10 UTC | May 31, 18:55 UTC | 1h 45m |
| 2026-05-30 | CFMBO | YWG → YWG | May 30, 20:55 UTC | May 31, 01:11 UTC | 4h 16m |
| 2026-05-30 | CFMBO | YWG → YWG | May 30, 06:35 UTC | May 30, 11:35 UTC | 5h 0m |
| 2026-05-29 | CFMBO | - | May 29, 03:30 UTC | May 29, 07:30 UTC | 4h 0m |
| 2026-05-29 | CFMBO | - | May 29, 02:50 UTC | May 29, 03:00 UTC | 10m |
| 2026-05-29 | CFMBO | - | May 29, 00:45 UTC | May 29, 01:25 UTC | 40m |
| 2026-05-27 | CFMBO | - | May 27, 13:40 UTC | May 27, 16:20 UTC | 2h 40m |
| 2026-05-27 | CFMBO | - | May 27, 03:24 UTC | May 27, 12:45 UTC | 9h 20m |
| 2026-05-26 | CFMBO | - | May 26, 10:20 UTC | May 26, 12:54 UTC | 2h 35m |
| 2026-05-26 | CFMBO | - | May 26, 01:05 UTC | May 26, 08:59 UTC | 7h 55m |
| 2026-05-21 | CFMBO | - | May 21, 10:10 UTC | May 21, 10:50 UTC | 40m |
| 2026-05-21 | CFMBO | - | May 21, 07:40 UTC | May 21, 07:45 UTC | 5m |
| 2026-05-21 | CFMBO | - | May 21, 05:40 UTC | May 21, 06:15 UTC | 35m |
| 2026-05-14 | CFMBO | - | May 14, 19:50 UTC | May 14, 22:20 UTC | 2h 30m |
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-FMBO page for operator, model, and routing details .