sensors Mode-S transponder
C0332C
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FTJV · BOEING 737 MAX 8 · operated by Air Canada
- Hex
- C0332C
- Octal
- 60031454
- Decimal
- 12,596,012
- Country
- CA
- Tail
- C-FTJV
- Type
- B38M
- Flights observed
- 440
- Distinct callsigns
- 20
- Country
- CA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C0332C 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 |
|---|---|---|---|
| ROU1784 | - | 41 | 2026-07-05 |
| ROU1783 | - | 39 | 2026-07-05 |
| ROU2096 | - | 17 | 2026-07-09 |
| ROU2097 | - | 14 | 2026-07-10 |
| ROU2078 | - | 14 | 2026-07-12 |
| ROU1769 | - | 14 | 2026-07-11 |
| ROU1768 | - | 14 | 2026-07-10 |
| ROU2077 | - | 13 | 2026-06-30 |
| ROU2074 | Transportes Aereos I.R. Crusoe | 13 | 2026-07-06 |
| ROU1743 | - | 13 | 2026-06-27 |
| ROU1742 | - | 13 | 2026-07-04 |
| ROU2129 | Transportes Aereos I.R. Crusoe | 12 | 2026-06-13 |
| ROU2028 | - | 12 | 2026-07-13 |
| ROU2128 | Transportes Aereos I.R. Crusoe | 11 | 2026-06-13 |
| ROU2073 | - | 10 | 2026-07-13 |
| ROU2081 | Transportes Aereos I.R. Crusoe | 9 | 2026-06-26 |
| ROU1775 | Transportes Aereos I.R. Crusoe | 8 | 2026-05-11 |
| ROU1755 | - | 8 | 2026-06-28 |
| ROU1754 | - | 8 | 2026-06-28 |
| ROU2018 | - | 7 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | ROU2073 | YYC → YVR | Jul 13, 04:37 UTC | Jul 13, 05:42 UTC | 1h 5m |
| 2026-07-13 | ROU2073 | YYC → YVR | Jul 13, 04:40 UTC | Jul 13, 05:55 UTC | 1h 15m |
| 2026-07-13 | ROU2028 | - | Jul 13, 01:45 UTC | Jul 13, 02:45 UTC | 1h 0m |
| 2026-07-12 | ROU2085 | - | Jul 12, 23:05 UTC | Jul 13, 00:35 UTC | 1h 30m |
| 2026-07-12 | ROU2078 | - | Jul 12, 20:30 UTC | Jul 12, 21:30 UTC | 1h 0m |
| 2026-07-12 | ROU2019 | YYC → YVR | Jul 12, 14:25 UTC | Jul 12, 15:40 UTC | 1h 15m |
| 2026-07-12 | ROU2072 | - | Jul 12, 04:20 UTC | Jul 12, 05:01 UTC | 40m |
| 2026-07-12 | ROU2072 | YVR → YYC | Jul 12, 04:20 UTC | Jul 12, 05:12 UTC | 52m |
| 2026-07-11 | ROU2132 | YVR → YVR | Jul 11, 16:15 UTC | Jul 12, 02:30 UTC | 10h 15m |
| 2026-07-11 | ROU1769 | - | Jul 11, 00:05 UTC | Jul 11, 01:00 UTC | 55m |
| 2026-07-11 | ROU1769 | SFO → YVR | Jul 11, 00:04 UTC | Jul 11, 01:36 UTC | 1h 32m |
| 2026-07-10 | ROU1768 | - | Jul 10, 22:40 UTC | Jul 10, 22:50 UTC | 10m |
| 2026-07-10 | ROU1768 | YVR → SFO | Jul 10, 20:30 UTC | Jul 10, 22:23 UTC | 1h 53m |
| 2026-07-10 | ROU1768 | YVR → SFO | Jul 10, 20:30 UTC | Jul 10, 22:50 UTC | 2h 20m |
| 2026-07-10 | ROU2097 | - | Jul 10, 13:50 UTC | Jul 10, 18:55 UTC | 5h 5m |
| 2026-07-10 | ROU1889 | YYZ → MEX | Jul 10, 00:55 UTC | Jul 10, 05:25 UTC | 4h 30m |
| 2026-07-09 | ROU1886 | - | Jul 9, 19:05 UTC | Jul 9, 23:10 UTC | 4h 5m |
| 2026-07-09 | ROU1887 | YYZ → MEX | Jul 9, 12:20 UTC | Jul 9, 16:40 UTC | 4h 20m |
| 2026-07-09 | ROU1888 | - | Jul 9, 06:45 UTC | Jul 9, 10:55 UTC | 4h 10m |
| 2026-07-09 | ROU2096 | - | Jul 9, 04:35 UTC | Jul 9, 04:50 UTC | 15m |
| 2026-07-09 | ROU2096 | - | Jul 9, 00:00 UTC | Jul 9, 03:50 UTC | 3h 50m |
| 2026-07-08 | ROU2075 | - | Jul 8, 12:20 UTC | Jul 8, 13:45 UTC | 1h 25m |
| 2026-07-08 | ROU2084 | - | Jul 8, 04:00 UTC | Jul 8, 05:10 UTC | 1h 10m |
| 2026-07-08 | ROU2084 | YVR → YEG | Jul 8, 04:00 UTC | Jul 8, 05:00 UTC | 1h 0m |
| 2026-07-08 | ROU2029 | YYC → YVR | Jul 8, 01:35 UTC | Jul 8, 02:40 UTC | 1h 5m |
| 2026-07-07 | ROU2026 | - | Jul 7, 23:10 UTC | Jul 8, 00:10 UTC | 1h 0m |
| 2026-07-07 | ROU2026 | YVR → YYC | Jul 7, 23:08 UTC | Jul 8, 00:05 UTC | 57m |
| 2026-07-07 | ROU2025 | YYC → YVR | Jul 7, 20:28 UTC | Jul 7, 21:31 UTC | 1h 3m |
| 2026-07-07 | ROU2025 | YYC → YVR | Jul 7, 20:30 UTC | Jul 7, 21:35 UTC | 1h 5m |
| 2026-07-07 | ROU2022 | YVR → YYC | Jul 7, 18:10 UTC | Jul 7, 19:10 UTC | 1h 0m |
| 2026-07-07 | ROU2019 | YFC → YYZ | Jul 7, 14:30 UTC | Jul 7, 15:40 UTC | 1h 10m |
| 2026-07-07 | ROU2028 | - | Jul 7, 01:30 UTC | Jul 7, 02:35 UTC | 1h 5m |
| 2026-07-06 | ROU2085 | - | Jul 6, 23:00 UTC | Jul 7, 00:15 UTC | 1h 15m |
| 2026-07-06 | ROU2078 | - | Jul 6, 20:30 UTC | Jul 6, 21:40 UTC | 1h 10m |
| 2026-07-06 | ROU2079 | - | Jul 6, 17:45 UTC | Jul 6, 19:00 UTC | 1h 15m |
| 2026-07-06 | ROU2074 | YVR → YEG | Jul 6, 14:35 UTC | Jul 6, 15:45 UTC | 1h 10m |
| 2026-07-05 | ROU2139 | IAH → YVR | Jul 5, 22:45 UTC | Jul 6, 03:10 UTC | 4h 25m |
| 2026-07-05 | ROU2138 | YVR → IAH | Jul 5, 17:05 UTC | Jul 5, 21:00 UTC | 3h 55m |
| 2026-07-05 | ROU1784 | - | Jul 5, 13:35 UTC | Jul 5, 14:10 UTC | 35m |
| 2026-07-05 | ROU1784 | - | Jul 5, 08:40 UTC | Jul 5, 08:50 UTC | 10m |
| 2026-07-05 | ROU1783 | - | Jul 5, 06:05 UTC | Jul 5, 06:25 UTC | 20m |
| 2026-07-05 | ROU1783 | YVR → HNL | Jul 5, 00:43 UTC | Jul 5, 06:27 UTC | 5h 44m |
| 2026-07-05 | ROU1783 | - | Jul 5, 00:45 UTC | Jul 5, 01:40 UTC | 55m |
| 2026-07-04 | ROU1745 | - | Jul 4, 19:45 UTC | Jul 4, 22:05 UTC | 2h 20m |
| 2026-07-04 | ROU1742 | - | Jul 4, 15:50 UTC | Jul 4, 18:15 UTC | 2h 25m |
| 2026-07-03 | ROU2139 | IAH → YVR | Jul 3, 22:50 UTC | Jul 4, 03:10 UTC | 4h 20m |
| 2026-07-03 | ROU2138 | YVR → IAH | Jul 3, 17:25 UTC | Jul 3, 21:20 UTC | 3h 55m |
| 2026-07-03 | ROU2019 | YFC → YYZ | Jul 3, 14:20 UTC | Jul 3, 15:30 UTC | 1h 10m |
| 2026-07-03 | ROU2028 | - | Jul 3, 02:40 UTC | Jul 3, 03:40 UTC | 1h 0m |
| 2026-07-02 | ROU2085 | YYC → YVR | Jul 2, 23:55 UTC | Jul 3, 01:15 UTC | 1h 20m |
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-FTJV page for operator, model, and routing details .