sensors Mode-S transponder
C05DF9
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GJPG · DASSAULT Falcon 900 · operated by Great Pacific Capital Corp. (Pattison Airways)
- Hex
- C05DF9
- Octal
- 60056771
- Decimal
- 12,606,969
- Country
- CA
- Tail
- C-GJPG
- Type
- F900
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address C05DF9 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 |
|---|---|---|---|
| CGJPG | - | 49 | 2026-07-14 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CGJPG | ANC → AKN | Jul 14, 20:55 UTC | Jul 14, 21:40 UTC | 45m |
| 2026-07-14 | CGJPG | - | Jul 14, 18:20 UTC | Jul 14, 19:10 UTC | 50m |
| 2026-07-14 | CGJPG | - | Jul 14, 14:05 UTC | Jul 14, 18:00 UTC | 3h 55m |
| 2026-07-09 | CGJPG | - | Jul 9, 00:00 UTC | Jul 9, 01:05 UTC | 1h 5m |
| 2026-07-08 | CGJPG | YVR → YYC | Jul 8, 17:45 UTC | Jul 8, 18:45 UTC | 1h 0m |
| 2026-06-30 | CGJPG | - | Jun 30, 19:30 UTC | Jun 30, 21:55 UTC | 2h 25m |
| 2026-06-26 | CGJPG | - | Jun 26, 21:24 UTC | Jun 26, 23:30 UTC | 2h 5m |
| 2026-06-18 | CGJPG | - | Jun 18, 22:20 UTC | Jun 19, 00:05 UTC | 1h 45m |
| 2026-06-18 | CGJPG | - | Jun 18, 20:10 UTC | Jun 18, 21:35 UTC | 1h 25m |
| 2026-06-17 | CGJPG | - | Jun 17, 22:35 UTC | Jun 17, 23:00 UTC | 25m |
| 2026-06-17 | CGJPG | - | Jun 17, 18:05 UTC | Jun 17, 18:35 UTC | 30m |
| 2026-06-17 | CGJPG | - | Jun 17, 13:25 UTC | Jun 17, 16:20 UTC | 2h 55m |
| 2026-06-16 | CGJPG | - | Jun 16, 20:20 UTC | Jun 16, 21:45 UTC | 1h 25m |
| 2026-06-15 | CGJPG | - | Jun 15, 21:25 UTC | Jun 15, 21:45 UTC | 20m |
| 2026-06-15 | CGJPG | - | Jun 15, 13:30 UTC | Jun 15, 15:10 UTC | 1h 40m |
| 2026-06-14 | CGJPG | - | Jun 14, 22:30 UTC | Jun 15, 00:05 UTC | 1h 35m |
| 2026-06-13 | CGJPG | - | Jun 13, 00:20 UTC | Jun 13, 00:45 UTC | 25m |
| 2026-06-12 | CGJPG | - | Jun 12, 22:55 UTC | Jun 12, 23:55 UTC | 1h 0m |
| 2026-06-12 | CGJPG | - | Jun 12, 18:05 UTC | Jun 12, 22:20 UTC | 4h 15m |
| 2026-06-11 | CGJPG | - | Jun 11, 17:10 UTC | Jun 11, 20:55 UTC | 3h 45m |
| 2026-06-11 | CGJPG | - | Jun 11, 15:45 UTC | Jun 11, 16:35 UTC | 50m |
| 2026-06-11 | CGJPG | - | Jun 11, 14:45 UTC | Jun 11, 15:15 UTC | 30m |
| 2026-06-07 | CGJPG | - | Jun 7, 18:20 UTC | Jun 7, 19:00 UTC | 40m |
| 2026-06-05 | CGJPG | - | Jun 5, 20:20 UTC | Jun 5, 20:50 UTC | 30m |
| 2026-06-04 | CGJPG | - | Jun 4, 13:15 UTC | Jun 4, 17:30 UTC | 4h 15m |
| 2026-06-01 | CGJPG | - | Jun 1, 19:50 UTC | Jun 1, 23:55 UTC | 4h 5m |
| 2026-05-20 | CGJPG | - | May 20, 17:00 UTC | May 20, 17:30 UTC | 30m |
| 2026-05-20 | CGJPG | - | May 20, 00:05 UTC | May 20, 01:45 UTC | 1h 40m |
| 2026-05-19 | CGJPG | - | May 19, 18:00 UTC | May 19, 18:15 UTC | 15m |
| 2026-05-18 | CGJPG | - | May 18, 21:35 UTC | May 19, 01:30 UTC | 3h 55m |
| 2026-05-18 | CGJPG | - | May 18, 15:45 UTC | May 18, 17:35 UTC | 1h 50m |
| 2026-05-17 | CGJPG | - | May 17, 19:15 UTC | May 17, 22:05 UTC | 2h 50m |
| 2026-05-17 | CGJPG | - | May 17, 18:25 UTC | May 17, 18:45 UTC | 20m |
| 2026-05-14 | CGJPG | - | May 14, 18:25 UTC | May 14, 20:15 UTC | 1h 50m |
| 2026-05-14 | CGJPG | - | May 14, 12:05 UTC | May 14, 14:45 UTC | 2h 40m |
| 2026-05-13 | CGJPG | EDI → YUL | May 13, 08:35 UTC | May 13, 14:40 UTC | 6h 5m |
| 2026-05-12 | CGJPG | - | May 12, 08:10 UTC | May 12, 09:15 UTC | 1h 5m |
| 2026-05-09 | CGJPG | - | May 9, 23:15 UTC | May 10, 07:50 UTC | 8h 35m |
| 2026-05-08 | CGJPG | - | May 8, 22:40 UTC | May 8, 22:50 UTC | 10m |
| 2026-05-08 | CGJPG | - | May 8, 17:00 UTC | May 8, 17:55 UTC | 55m |
| 2026-05-07 | CGJPG | - | May 7, 21:50 UTC | May 7, 22:35 UTC | 45m |
| 2026-05-07 | CGJPG | - | May 7, 13:35 UTC | May 7, 14:05 UTC | 30m |
| 2026-04-17 | CGJPG | - | Apr 17, 19:25 UTC | Apr 17, 19:30 UTC | 5m |
| 2026-04-17 | CGJPG | - | Apr 17, 17:30 UTC | Apr 17, 19:20 UTC | 1h 50m |
| 2026-04-17 | CGJPG | - | Apr 17, 15:20 UTC | Apr 17, 16:55 UTC | 1h 35m |
| 2026-04-17 | CGJPG | - | Apr 17, 13:40 UTC | Apr 17, 15:15 UTC | 1h 35m |
| 2026-04-15 | CGJPG | - | Apr 15, 21:05 UTC | Apr 15, 21:50 UTC | 45m |
| 2026-04-15 | CGJPG | - | Apr 15, 19:05 UTC | Apr 15, 21:00 UTC | 1h 55m |
| 2026-04-15 | CGJPG | - | Apr 15, 17:05 UTC | Apr 15, 18:05 UTC | 1h 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-GJPG page for operator, model, and routing details .