sensors Mode-S transponder
C087D7
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GZLM · BOMBARDIER BD-700 Global 6000/6500 · operated by 2106701 Ontario Inc (NOVAJET)
- Hex
- C087D7
- Octal
- 60103727
- Decimal
- 12,617,687
- Country
- CA
- Tail
- C-GZLM
- Type
- GLEX
- Flights observed
- 53
- Distinct callsigns
- 3
- Country
- CA
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address C087D7 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CGZLM | - | Jul 17, 13:50 UTC | Jul 17, 20:29 UTC | 6h 40m |
| 2026-07-17 | CGZLM | MME → STN | Jul 17, 06:35 UTC | Jul 17, 07:25 UTC | 50m |
| 2026-07-13 | NOJ61 | - | Jul 13, 09:20 UTC | Jul 13, 11:45 UTC | 2h 25m |
| 2026-07-12 | NOJ921G | - | Jul 12, 23:30 UTC | Jul 13, 06:25 UTC | 6h 55m |
| 2026-07-11 | CGZLM | - | Jul 11, 16:30 UTC | Jul 11, 23:55 UTC | 7h 25m |
| 2026-07-11 | CGZLM | - | Jul 11, 13:00 UTC | Jul 11, 14:50 UTC | 1h 50m |
| 2026-07-05 | CGZLM | - | Jul 5, 16:25 UTC | Jul 5, 17:25 UTC | 1h 0m |
| 2026-07-05 | CGZLM | - | Jul 5, 13:30 UTC | Jul 5, 14:20 UTC | 50m |
| 2026-07-05 | CGZLM | - | Jul 5, 10:30 UTC | Jul 5, 10:55 UTC | 25m |
| 2026-07-02 | CGZLM | - | Jul 2, 08:35 UTC | Jul 2, 08:55 UTC | 20m |
| 2026-07-02 | CGZLM | - | Jul 2, 04:15 UTC | Jul 2, 06:35 UTC | 2h 20m |
| 2026-07-01 | CGZLM | - | Jul 1, 23:35 UTC | Jul 2, 01:00 UTC | 1h 25m |
| 2026-06-30 | CGZLM | - | Jun 30, 21:45 UTC | Jun 30, 21:55 UTC | 10m |
| 2026-06-30 | CGZLM | - | Jun 30, 20:25 UTC | Jun 30, 21:10 UTC | 45m |
| 2026-06-29 | CGZLM | - | Jun 29, 11:45 UTC | Jun 29, 12:34 UTC | 50m |
| 2026-06-26 | CGZLM | - | Jun 26, 18:24 UTC | Jun 26, 19:09 UTC | 45m |
| 2026-06-26 | CGZLM | YHU → YUL | Jun 26, 17:50 UTC | Jun 26, 17:59 UTC | 10m |
| 2026-06-26 | CGZLM | YQB → YHU | Jun 26, 02:05 UTC | Jun 26, 02:34 UTC | 30m |
| 2026-06-25 | CGZLM | - | Jun 25, 12:54 UTC | Jun 25, 13:24 UTC | 30m |
| 2026-06-25 | CGZLM | - | Jun 25, 11:44 UTC | Jun 25, 12:35 UTC | 50m |
| 2026-06-24 | CGZLM | YYZ → YPD | Jun 24, 22:45 UTC | Jun 24, 23:14 UTC | 30m |
| 2026-06-23 | CGZLM | YHU → YYZ | Jun 23, 20:34 UTC | Jun 23, 22:10 UTC | 1h 35m |
| 2026-06-22 | CGZLM | - | Jun 22, 12:00 UTC | Jun 22, 12:44 UTC | 45m |
| 2026-06-18 | CGZLM | - | Jun 18, 20:50 UTC | Jun 18, 21:10 UTC | 20m |
| 2026-06-17 | CGZLM | - | Jun 17, 20:45 UTC | Jun 17, 21:35 UTC | 50m |
| 2026-06-16 | CGZLM | YYZ → YHU | Jun 16, 12:35 UTC | Jun 16, 13:30 UTC | 55m |
| 2026-06-15 | CGZLM | - | Jun 15, 11:49 UTC | Jun 15, 12:15 UTC | 25m |
| 2026-06-12 | CGZLM | - | Jun 12, 12:15 UTC | Jun 12, 18:50 UTC | 6h 35m |
| 2026-06-10 | CGZLM | - | Jun 10, 15:15 UTC | Jun 10, 16:15 UTC | 1h 0m |
| 2026-06-09 | CGZLM | - | Jun 9, 14:50 UTC | Jun 9, 15:45 UTC | 55m |
| 2026-06-08 | CGZLM | - | Jun 8, 16:05 UTC | Jun 8, 16:50 UTC | 45m |
| 2026-06-06 | CGZLM | - | Jun 6, 02:00 UTC | Jun 6, 08:00 UTC | 6h 0m |
| 2026-06-04 | CGZLM | - | Jun 4, 18:50 UTC | Jun 4, 19:55 UTC | 1h 5m |
| 2026-06-01 | CGZLM | - | Jun 1, 11:55 UTC | Jun 1, 12:55 UTC | 1h 0m |
| 2026-05-29 | CGZLM | - | May 29, 16:35 UTC | May 29, 16:55 UTC | 20m |
| 2026-05-27 | CGZLM | YHU → YYZ | May 27, 22:35 UTC | May 27, 23:35 UTC | 1h 0m |
| 2026-05-25 | CGZLM | - | May 25, 11:50 UTC | May 25, 13:35 UTC | 1h 45m |
| 2026-05-22 | CGZLM | - | May 22, 18:45 UTC | May 22, 19:50 UTC | 1h 5m |
| 2026-05-19 | CGZLM | BQH → YQB | May 19, 18:20 UTC | May 20, 00:30 UTC | 6h 10m |
| 2026-05-16 | CGZLM | LBA → BQH | May 16, 07:35 UTC | May 16, 08:20 UTC | 45m |
| 2026-05-09 | CGZLM | - | May 9, 00:50 UTC | May 9, 06:15 UTC | 5h 25m |
| 2026-05-08 | CGZLM | - | May 8, 22:55 UTC | May 8, 23:55 UTC | 1h 0m |
| 2026-05-04 | CGZLM | - | May 4, 10:50 UTC | May 4, 13:15 UTC | 2h 25m |
| 2026-05-04 | CGZLM | YYZ → YYZ | May 4, 10:10 UTC | May 4, 10:15 UTC | 5m |
| 2026-05-01 | CGZLM | - | May 1, 02:45 UTC | May 1, 03:35 UTC | 50m |
| 2026-04-30 | CGZLM | - | Apr 30, 20:50 UTC | Apr 30, 21:20 UTC | 30m |
| 2026-04-30 | CGZLM | YYZ → YQB | Apr 30, 19:20 UTC | Apr 30, 20:15 UTC | 55m |
| 2026-04-27 | CGZLM | - | Apr 27, 11:10 UTC | Apr 27, 13:40 UTC | 2h 30m |
| 2026-04-24 | CGZLM | - | Apr 24, 19:00 UTC | Apr 24, 20:05 UTC | 1h 5m |
| 2026-04-24 | CGZLM | - | Apr 24, 16:45 UTC | Apr 24, 17:45 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-GZLM page for operator, model, and routing details .