sensors Mode-S transponder
C033F6
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FTRP · GULFSTREAM G150 · operated by TransCanada PipeLines Limited
- Hex
- C033F6
- Octal
- 60031766
- Decimal
- 12,596,214
- Country
- CA
- Tail
- C-FTRP
- Type
- G150
- Flights observed
- 45
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- Jul 23, 21:30 UTC
Last known position
Country allocation
The ICAO 24-bit address C033F6 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 |
|---|---|---|---|
| CFTRP | - | 45 | 2026-07-23 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | CFTRP | - | Jul 23, 17:35 UTC | Jul 23, 21:25 UTC | 3h 50m |
| 2026-07-21 | CFTRP | - | Jul 21, 13:15 UTC | Jul 21, 16:00 UTC | 2h 45m |
| 2026-07-19 | CFTRP | TEB → YYC | Jul 19, 22:50 UTC | Jul 20, 03:50 UTC | 5h 0m |
| 2026-07-19 | CFTRP | - | Jul 19, 13:45 UTC | Jul 19, 16:15 UTC | 2h 30m |
| 2026-07-17 | CFTRP | - | Jul 17, 17:50 UTC | Jul 17, 19:20 UTC | 1h 30m |
| 2026-07-15 | CFTRP | - | Jul 15, 13:45 UTC | Jul 15, 16:45 UTC | 3h 0m |
| 2026-07-05 | CFTRP | - | Jul 5, 15:30 UTC | Jul 5, 20:40 UTC | 5h 10m |
| 2026-06-26 | CFTRP | - | Jun 26, 17:50 UTC | Jun 26, 22:10 UTC | 4h 20m |
| 2026-06-20 | CFTRP | - | Jun 20, 19:34 UTC | Jun 20, 21:44 UTC | 2h 10m |
| 2026-06-19 | CFTRP | - | Jun 19, 17:09 UTC | Jun 19, 17:49 UTC | 40m |
| 2026-06-19 | CFTRP | - | Jun 19, 14:34 UTC | Jun 19, 16:14 UTC | 1h 40m |
| 2026-06-13 | CFTRP | - | Jun 13, 00:20 UTC | Jun 13, 02:40 UTC | 2h 20m |
| 2026-06-12 | CFTRP | - | Jun 12, 21:55 UTC | Jun 12, 23:15 UTC | 1h 20m |
| 2026-06-12 | CFTRP | - | Jun 12, 20:10 UTC | Jun 12, 21:25 UTC | 1h 15m |
| 2026-06-10 | CFTRP | MDW → YYC | Jun 10, 23:15 UTC | Jun 11, 02:15 UTC | 3h 0m |
| 2026-06-08 | CFTRP | YYC → MDW | Jun 8, 17:15 UTC | Jun 8, 20:25 UTC | 3h 10m |
| 2026-06-07 | CFTRP | - | Jun 7, 22:45 UTC | Jun 8, 01:45 UTC | 3h 0m |
| 2026-06-07 | CFTRP | YYC → MDW | Jun 7, 18:10 UTC | Jun 7, 21:30 UTC | 3h 20m |
| 2026-06-04 | CFTRP | - | Jun 4, 16:25 UTC | Jun 4, 20:25 UTC | 4h 0m |
| 2026-06-03 | CFTRP | - | Jun 3, 21:40 UTC | Jun 3, 22:35 UTC | 55m |
| 2026-06-01 | CFTRP | - | Jun 1, 19:15 UTC | Jun 1, 20:55 UTC | 1h 40m |
| 2026-05-28 | CFTRP | - | May 28, 17:35 UTC | May 28, 19:15 UTC | 1h 40m |
| 2026-05-25 | CFTRP | - | May 25, 21:30 UTC | May 26, 01:55 UTC | 4h 25m |
| 2026-05-25 | CFTRP | - | May 25, 17:50 UTC | May 25, 19:10 UTC | 1h 20m |
| 2026-05-25 | CFTRP | YYC → BOI | May 25, 16:00 UTC | May 25, 17:15 UTC | 1h 15m |
| 2026-05-15 | CFTRP | - | May 15, 20:15 UTC | May 15, 22:25 UTC | 2h 10m |
| 2026-05-15 | CFTRP | - | May 15, 17:35 UTC | May 15, 18:55 UTC | 1h 20m |
| 2026-05-15 | CFTRP | - | May 15, 15:50 UTC | May 15, 17:05 UTC | 1h 15m |
| 2026-05-12 | CFTRP | - | May 12, 21:45 UTC | May 12, 23:35 UTC | 1h 50m |
| 2026-05-12 | CFTRP | YYC → YWG | May 12, 12:10 UTC | May 12, 13:45 UTC | 1h 35m |
| 2026-05-09 | CFTRP | YVR → YYC | May 9, 03:10 UTC | May 9, 04:05 UTC | 55m |
| 2026-05-07 | CFTRP | - | May 7, 19:15 UTC | May 7, 20:20 UTC | 1h 5m |
| 2026-04-27 | CFTRP | - | Apr 27, 19:00 UTC | Apr 27, 22:50 UTC | 3h 50m |
| 2026-04-26 | CFTRP | - | Apr 26, 22:05 UTC | Apr 27, 02:20 UTC | 4h 15m |
| 2026-04-22 | CFTRP | - | Apr 22, 22:10 UTC | Apr 23, 00:45 UTC | 2h 35m |
| 2026-04-21 | CFTRP | - | Apr 21, 15:10 UTC | Apr 21, 19:20 UTC | 4h 10m |
| 2026-04-20 | CFTRP | YYC → YOW | Apr 20, 17:00 UTC | Apr 20, 20:25 UTC | 3h 25m |
| 2026-04-16 | CFTRP | - | Apr 16, 19:15 UTC | Apr 16, 20:20 UTC | 1h 5m |
| 2026-04-16 | CFTRP | - | Apr 16, 17:15 UTC | Apr 16, 19:10 UTC | 1h 55m |
| 2026-04-16 | CFTRP | - | Apr 16, 16:35 UTC | Apr 16, 17:10 UTC | 35m |
| 2026-04-14 | CFTRP | - | Apr 14, 16:50 UTC | Apr 14, 17:25 UTC | 35m |
| 2026-04-14 | CFTRP | - | Apr 14, 14:50 UTC | Apr 14, 16:45 UTC | 1h 55m |
| 2026-04-14 | CFTRP | - | Apr 14, 14:05 UTC | Apr 14, 14:45 UTC | 40m |
| 2026-04-13 | CFTRP | - | Apr 13, 19:50 UTC | Apr 13, 20:15 UTC | 25m |
| 2026-04-13 | CFTRP | - | Apr 13, 19:40 UTC | Apr 13, 19:45 UTC | 5m |
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-FTRP page for operator, model, and routing details .