sensors Mode-S transponder
C05E9B
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GJVM · PILATUS PC-12 · operated by 9215-4400 Qubec Inc. (UNIVAIR AVIATION)
- Hex
- C05E9B
- Octal
- 60057233
- Decimal
- 12,607,131
- Country
- CA
- Tail
- C-GJVM
- Type
- PC12
- Flights observed
- 42
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address C05E9B 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 |
|---|---|---|---|
| CGJVM | - | 42 | 2026-06-08 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | CGJVM | - | Jun 8, 11:10 UTC | Jun 8, 13:00 UTC | 1h 50m |
| 2026-06-08 | CGJVM | - | Jun 8, 10:00 UTC | Jun 8, 10:25 UTC | 25m |
| 2026-06-08 | CGJVM | - | Jun 8, 03:05 UTC | Jun 8, 05:50 UTC | 2h 45m |
| 2026-06-07 | CGJVM | YHU → YHU | Jun 7, 17:00 UTC | Jun 7, 18:50 UTC | 1h 50m |
| 2026-06-07 | CGJVM | - | Jun 7, 12:20 UTC | Jun 7, 13:00 UTC | 40m |
| 2026-06-07 | CGJVM | - | Jun 7, 11:05 UTC | Jun 7, 11:45 UTC | 40m |
| 2026-06-06 | CGJVM | BOS → YHU | Jun 6, 21:04 UTC | Jun 6, 22:10 UTC | 1h 5m |
| 2026-06-06 | CGJVM | - | Jun 6, 18:39 UTC | Jun 6, 20:05 UTC | 1h 25m |
| 2026-06-05 | CGJVM | - | Jun 5, 19:25 UTC | Jun 5, 20:40 UTC | 1h 15m |
| 2026-06-05 | CGJVM | YHU → BED | Jun 5, 17:25 UTC | Jun 5, 18:25 UTC | 1h 0m |
| 2026-06-04 | CGJVM | - | Jun 4, 16:55 UTC | Jun 4, 18:45 UTC | 1h 50m |
| 2026-05-31 | CGJVM | - | May 31, 17:55 UTC | May 31, 19:20 UTC | 1h 25m |
| 2026-05-30 | CGJVM | - | May 30, 17:55 UTC | May 30, 19:15 UTC | 1h 20m |
| 2026-05-29 | CGJVM | - | May 29, 11:20 UTC | May 29, 12:20 UTC | 1h 0m |
| 2026-05-29 | CGJVM | BOS → YHU | May 29, 02:25 UTC | May 29, 03:40 UTC | 1h 15m |
| 2026-05-28 | CGJVM | YHU → BOS | May 28, 12:45 UTC | May 28, 13:50 UTC | 1h 5m |
| 2026-05-25 | CGJVM | - | May 25, 12:05 UTC | May 25, 13:15 UTC | 1h 10m |
| 2026-05-25 | CGJVM | - | May 25, 09:35 UTC | May 25, 10:35 UTC | 1h 0m |
| 2026-05-22 | CGJVM | - | May 22, 12:05 UTC | May 22, 13:25 UTC | 1h 20m |
| 2026-05-22 | CGJVM | YHU → YYZ | May 22, 09:50 UTC | May 22, 11:35 UTC | 1h 45m |
| 2026-05-20 | CGJVM | BOS → YHU | May 20, 14:10 UTC | May 20, 15:20 UTC | 1h 10m |
| 2026-05-19 | CGJVM | YHU → BOS | May 19, 19:35 UTC | May 19, 20:50 UTC | 1h 15m |
| 2026-05-18 | CGJVM | - | May 18, 20:05 UTC | May 18, 23:00 UTC | 2h 55m |
| 2026-05-15 | CGJVM | - | May 15, 01:35 UTC | May 15, 02:00 UTC | 25m |
| 2026-05-14 | CGJVM | YHU → RDU | May 14, 21:50 UTC | May 15, 00:50 UTC | 3h 0m |
| 2026-05-09 | CGJVM | - | May 9, 01:45 UTC | May 9, 02:50 UTC | 1h 5m |
| 2026-05-08 | CGJVM | YHU → BUF | May 8, 19:40 UTC | May 8, 21:05 UTC | 1h 25m |
| 2026-05-07 | CGJVM | BUF → YHU | May 7, 03:05 UTC | May 7, 04:10 UTC | 1h 5m |
| 2026-05-06 | CGJVM | YHU → BUF | May 6, 19:20 UTC | May 6, 20:50 UTC | 1h 30m |
| 2026-05-05 | CGJVM | YHU → YHU | May 5, 18:15 UTC | May 5, 19:55 UTC | 1h 40m |
| 2026-04-23 | CGJVM | - | Apr 23, 21:25 UTC | Apr 23, 22:40 UTC | 1h 15m |
| 2026-04-22 | CGJVM | - | Apr 22, 12:05 UTC | Apr 22, 13:30 UTC | 1h 25m |
| 2026-04-20 | CGJVM | - | Apr 20, 19:15 UTC | Apr 20, 20:05 UTC | 50m |
| 2026-04-20 | CGJVM | - | Apr 20, 14:55 UTC | Apr 20, 16:25 UTC | 1h 30m |
| 2026-04-20 | CGJVM | - | Apr 20, 13:00 UTC | Apr 20, 14:20 UTC | 1h 20m |
| 2026-04-20 | CGJVM | YHU → YHU | Apr 20, 08:35 UTC | Apr 20, 10:10 UTC | 1h 35m |
| 2026-04-16 | CGJVM | - | Apr 16, 15:15 UTC | Apr 16, 16:50 UTC | 1h 35m |
| 2026-04-16 | CGJVM | - | Apr 16, 11:20 UTC | Apr 16, 11:54 UTC | 35m |
| 2026-04-15 | CGJVM | - | Apr 15, 14:01 UTC | Apr 15, 14:15 UTC | 15m |
| 2026-04-14 | CGJVM | - | Apr 14, 13:35 UTC | Apr 14, 13:45 UTC | 10m |
| 2026-04-13 | CGJVM | - | Apr 13, 19:25 UTC | Apr 13, 19:40 UTC | 15m |
| 2026-04-12 | CGJVM | - | Apr 12, 17:15 UTC | Apr 12, 18:10 UTC | 55m |
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-GJVM page for operator, model, and routing details .