sensors Mode-S transponder
C0104F
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FGEO · BOEING 787-9 Dreamliner · operated by Air Canada
- Hex
- C0104F
- Octal
- 60010117
- Decimal
- 12,587,087
- Country
- CA
- Tail
- C-FGEO
- Type
- B789
- Flights observed
- 162
- Distinct callsigns
- 20
- Country
- CA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address C0104F 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ACA548 | Air Canada | 10 | 2026-06-12 |
| ACA9 | - | 9 | 2026-06-29 |
| ACA7 | Air Canada | 9 | 2026-07-01 |
| ACA10 | - | 9 | 2026-06-30 |
| ACA549 | Air Canada | 7 | 2026-06-13 |
| ACA8 | - | 6 | 2026-07-02 |
| ACA800 | - | 5 | 2026-06-27 |
| ACA36 | - | 5 | 2026-06-14 |
| ACA827 | Air Canada | 4 | 2026-05-25 |
| ACA801 | - | 4 | 2026-06-29 |
| ACA65 | Air Canada | 4 | 2026-06-02 |
| ACA35 | Air Canada | 4 | 2026-06-13 |
| ACA029 | - | 4 | 2026-06-21 |
| ACA026 | - | 4 | 2026-06-18 |
| ACA025 | Air Canada | 4 | 2026-06-17 |
| ACA916 | - | 3 | 2026-06-29 |
| ACA90 | Air Canada | 3 | 2026-05-27 |
| ACA807 | - | 3 | 2026-06-25 |
| ACA806 | - | 3 | 2026-06-25 |
| ACA61 | Air Canada | 3 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-05 | ACA888 | - | Jul 5, 01:15 UTC | Jul 5, 01:45 UTC | 30m |
| 2026-07-04 | ACA342 | YVR → YOW | Jul 4, 16:20 UTC | Jul 4, 20:00 UTC | 3h 40m |
| 2026-07-04 | ACA342 | YVR → YOW | Jul 4, 16:16 UTC | Jul 4, 19:59 UTC | 3h 43m |
| 2026-07-04 | ACA20 | - | Jul 4, 00:10 UTC | Jul 4, 13:55 UTC | 13h 45m |
| 2026-07-03 | ACA19 | - | Jul 3, 21:35 UTC | Jul 3, 21:45 UTC | 10m |
| 2026-07-03 | ACA19 | - | Jul 3, 06:15 UTC | Jul 3, 20:25 UTC | 14h 10m |
| 2026-07-02 | ACA8 | HKG → YVR | Jul 2, 02:00 UTC | Jul 2, 12:50 UTC | 10h 50m |
| 2026-07-02 | ACA8 | HKG → YVR | Jul 2, 01:59 UTC | Jul 2, 12:39 UTC | 10h 40m |
| 2026-07-01 | ACA7 | ICN → HKG | Jul 1, 20:45 UTC | Jul 1, 21:10 UTC | 25m |
| 2026-07-01 | ACA7 | ICN → HKG | Jul 1, 08:15 UTC | Jul 1, 20:15 UTC | 12h 0m |
| 2026-07-01 | ACA129 | YYZ → YVR | Jul 1, 00:55 UTC | Jul 1, 05:15 UTC | 4h 20m |
| 2026-06-30 | ACA10 | - | Jun 30, 08:40 UTC | Jun 30, 20:05 UTC | 11h 25m |
| 2026-06-29 | ACA9 | - | Jun 29, 18:14 UTC | Jun 30, 06:35 UTC | 12h 21m |
| 2026-06-29 | ACA801 | DUB → YYZ | Jun 29, 08:50 UTC | Jun 29, 15:14 UTC | 6h 25m |
| 2026-06-29 | ACA916 | - | Jun 29, 06:40 UTC | Jun 29, 06:44 UTC | 5m |
| 2026-06-29 | ACA916 | YUL → DUB | Jun 29, 01:25 UTC | Jun 29, 06:44 UTC | 5h 20m |
| 2026-06-29 | ACA916 | YUL → DUB | Jun 29, 01:20 UTC | Jun 29, 06:20 UTC | 5h 0m |
| 2026-06-28 | ACA68 | ICN → YUL | Jun 28, 09:25 UTC | Jun 28, 21:45 UTC | 12h 20m |
| 2026-06-27 | ACA67 | YUL → YVR | Jun 27, 17:25 UTC | Jun 28, 07:29 UTC | 14h 5m |
| 2026-06-27 | ACA917 | DUB → YUL | Jun 27, 09:09 UTC | Jun 27, 14:54 UTC | 5h 45m |
| 2026-06-27 | ACA800 | YYZ → DUB | Jun 27, 01:04 UTC | Jun 27, 06:54 UTC | 5h 50m |
| 2026-06-26 | ACA10 | - | Jun 26, 09:30 UTC | Jun 26, 20:44 UTC | 11h 15m |
| 2026-06-26 | ACA9 | - | Jun 26, 06:35 UTC | Jun 26, 06:54 UTC | 20m |
| 2026-06-25 | ACA9 | - | Jun 25, 18:04 UTC | Jun 25, 19:44 UTC | 1h 40m |
| 2026-06-25 | ACA9 | YYZ → NRT | Jun 25, 18:04 UTC | Jun 26, 06:19 UTC | 12h 15m |
| 2026-06-25 | ACA807 | EDI → YYZ | Jun 25, 08:40 UTC | Jun 25, 15:20 UTC | 6h 40m |
| 2026-06-25 | ACA806 | YYZ → EDI | Jun 25, 00:49 UTC | Jun 25, 06:40 UTC | 5h 50m |
| 2026-06-24 | ACA891 | - | Jun 24, 10:35 UTC | Jun 24, 19:10 UTC | 8h 35m |
| 2026-06-24 | ACA890 | - | Jun 24, 05:05 UTC | Jun 24, 07:59 UTC | 2h 55m |
| 2026-06-24 | ACA890 | - | Jun 24, 00:15 UTC | Jun 24, 01:44 UTC | 1h 30m |
| 2026-06-23 | ACA182 | YVR → YUL | Jun 23, 15:15 UTC | Jun 23, 19:04 UTC | 3h 50m |
| 2026-06-23 | ACA182 | YVR → YUL | Jun 23, 15:13 UTC | Jun 23, 18:55 UTC | 3h 42m |
| 2026-06-22 | ACA030 | - | Jun 22, 12:15 UTC | Jun 22, 21:30 UTC | 9h 15m |
| 2026-06-22 | ACA030 | PEK → YVR | Jun 22, 11:24 UTC | Jun 22, 21:23 UTC | 9h 59m |
| 2026-06-21 | ACA029 | - | Jun 21, 21:14 UTC | Jun 22, 07:54 UTC | 10h 40m |
| 2026-06-21 | ACA919 | MIA → YYZ | Jun 21, 09:20 UTC | Jun 21, 17:45 UTC | 8h 25m |
| 2026-06-21 | ACA800 | YYZ → DUB | Jun 21, 01:05 UTC | Jun 21, 06:55 UTC | 5h 50m |
| 2026-06-21 | ACA800 | YYZ → DUB | Jun 21, 01:05 UTC | Jun 21, 06:47 UTC | 5h 42m |
| 2026-06-20 | ACA10 | - | Jun 20, 08:29 UTC | Jun 20, 20:00 UTC | 11h 30m |
| 2026-06-19 | ACA9 | YYZ → NRT | Jun 19, 18:05 UTC | Jun 20, 06:10 UTC | 12h 5m |
| 2026-06-19 | ACA801 | - | Jun 19, 08:54 UTC | Jun 19, 15:09 UTC | 6h 15m |
| 2026-06-19 | ACA801 | DUB → YYZ | Jun 19, 08:53 UTC | Jun 19, 15:03 UTC | 6h 10m |
| 2026-06-18 | ACA918 | YYZ → MIA | Jun 18, 22:50 UTC | Jun 18, 23:45 UTC | 55m |
| 2026-06-18 | ACA918 | YYZ → MIA | Jun 18, 22:50 UTC | Jun 19, 06:57 UTC | 8h 7m |
| 2026-06-18 | ACA026 | - | Jun 18, 04:55 UTC | Jun 18, 20:15 UTC | 15h 20m |
| 2026-06-17 | ACA026 | - | Jun 17, 23:55 UTC | Jun 18, 20:15 UTC | 20h 20m |
| 2026-06-17 | ACA025 | YVR → PVG | Jun 17, 21:50 UTC | Jun 18, 20:15 UTC | 22h 25m |
| 2026-06-17 | ACA025 | YVR → PVG | Jun 17, 20:20 UTC | Jun 18, 19:45 UTC | 23h 25m |
| 2026-06-17 | ACA839 | FRA → YOW | Jun 17, 08:40 UTC | Jun 17, 18:10 UTC | 9h 30m |
| 2026-06-16 | ACA838 | YOW → FRA | Jun 16, 20:45 UTC | Jun 17, 05:45 UTC | 9h 0m |
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-FGEO page for operator, model, and routing details .