sensors Mode-S transponder
C04135
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FYSA · PIPER PA-44 Seminole · operated by Richcopter Inc.
- Hex
- C04135
- Octal
- 60040465
- Decimal
- 12,599,605
- Country
- CA
- Tail
- C-FYSA
- Type
- PA44
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address C04135 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 |
|---|---|---|---|
| CFYSA | - | 57 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | CFYSA | - | Jun 9, 15:30 UTC | Jun 9, 15:50 UTC | 20m |
| 2026-06-09 | CFYSA | - | Jun 9, 13:30 UTC | Jun 9, 14:15 UTC | 45m |
| 2026-06-08 | CFYSA | - | Jun 8, 23:45 UTC | Jun 9, 00:05 UTC | 20m |
| 2026-06-08 | CFYSA | - | Jun 8, 21:25 UTC | Jun 8, 22:25 UTC | 1h 0m |
| 2026-06-08 | CFYSA | - | Jun 8, 18:10 UTC | Jun 8, 18:55 UTC | 45m |
| 2026-06-08 | CFYSA | - | Jun 8, 12:25 UTC | Jun 8, 13:20 UTC | 55m |
| 2026-06-05 | CFYSA | - | Jun 5, 19:40 UTC | Jun 5, 20:40 UTC | 1h 0m |
| 2026-06-04 | CFYSA | - | Jun 4, 22:15 UTC | Jun 4, 23:25 UTC | 1h 10m |
| 2026-06-04 | CFYSA | - | Jun 4, 15:30 UTC | Jun 4, 16:10 UTC | 40m |
| 2026-06-04 | CFYSA | - | Jun 4, 12:50 UTC | Jun 4, 13:40 UTC | 50m |
| 2026-06-03 | CFYSA | - | Jun 3, 19:05 UTC | Jun 3, 20:30 UTC | 1h 25m |
| 2026-06-03 | CFYSA | - | Jun 3, 15:25 UTC | Jun 3, 16:40 UTC | 1h 15m |
| 2026-06-02 | CFYSA | - | Jun 2, 21:45 UTC | Jun 2, 23:00 UTC | 1h 15m |
| 2026-06-02 | CFYSA | - | Jun 2, 19:00 UTC | Jun 2, 19:40 UTC | 40m |
| 2026-06-02 | CFYSA | - | Jun 2, 15:25 UTC | Jun 2, 16:15 UTC | 50m |
| 2026-06-02 | CFYSA | - | Jun 2, 13:25 UTC | Jun 2, 14:05 UTC | 40m |
| 2026-06-01 | CFYSA | - | Jun 1, 23:10 UTC | Jun 2, 00:55 UTC | 1h 45m |
| 2026-05-31 | CFYSA | - | May 31, 11:45 UTC | May 31, 13:05 UTC | 1h 20m |
| 2026-05-30 | CFYSA | - | May 30, 12:35 UTC | May 30, 13:25 UTC | 50m |
| 2026-05-29 | CFYSA | - | May 29, 14:55 UTC | May 29, 16:15 UTC | 1h 20m |
| 2026-05-29 | CFYSA | - | May 29, 12:25 UTC | May 29, 13:40 UTC | 1h 15m |
| 2026-05-27 | CFYSA | - | May 27, 21:00 UTC | May 27, 22:10 UTC | 1h 10m |
| 2026-05-27 | CFYSA | - | May 27, 17:45 UTC | May 27, 19:00 UTC | 1h 15m |
| 2026-05-27 | CFYSA | - | May 27, 15:35 UTC | May 27, 16:25 UTC | 50m |
| 2026-05-27 | CFYSA | - | May 27, 13:10 UTC | May 27, 14:15 UTC | 1h 5m |
| 2026-05-26 | CFYSA | - | May 26, 15:29 UTC | May 26, 16:20 UTC | 50m |
| 2026-05-26 | CFYSA | - | May 26, 12:45 UTC | May 26, 13:50 UTC | 1h 5m |
| 2026-05-26 | CFYSA | - | May 26, 01:55 UTC | May 26, 03:55 UTC | 2h 0m |
| 2026-05-25 | CFYSA | - | May 25, 23:35 UTC | May 26, 00:39 UTC | 1h 5m |
| 2026-05-13 | CFYSA | - | May 13, 02:35 UTC | May 13, 04:20 UTC | 1h 45m |
| 2026-05-09 | CFYSA | - | May 9, 03:55 UTC | May 9, 05:00 UTC | 1h 5m |
| 2026-05-07 | CFYSA | - | May 7, 16:00 UTC | May 7, 16:50 UTC | 50m |
| 2026-05-06 | CFYSA | - | May 6, 20:20 UTC | May 6, 21:15 UTC | 55m |
| 2026-05-06 | CFYSA | - | May 6, 17:55 UTC | May 6, 19:05 UTC | 1h 10m |
| 2026-05-06 | CFYSA | - | May 6, 14:30 UTC | May 6, 14:45 UTC | 15m |
| 2026-05-01 | CFYSA | - | May 1, 16:00 UTC | May 1, 17:00 UTC | 1h 0m |
| 2026-04-30 | CFYSA | - | Apr 30, 20:40 UTC | Apr 30, 21:50 UTC | 1h 10m |
| 2026-04-29 | CFYSA | - | Apr 29, 22:05 UTC | Apr 29, 22:15 UTC | 10m |
| 2026-04-29 | CFYSA | - | Apr 29, 21:05 UTC | Apr 29, 21:20 UTC | 15m |
| 2026-04-29 | CFYSA | - | Apr 29, 17:30 UTC | Apr 29, 19:55 UTC | 2h 25m |
| 2026-04-27 | CFYSA | - | Apr 27, 18:40 UTC | Apr 27, 20:00 UTC | 1h 20m |
| 2026-04-25 | CFYSA | - | Apr 25, 15:05 UTC | Apr 25, 16:10 UTC | 1h 5m |
| 2026-04-25 | CFYSA | - | Apr 25, 13:00 UTC | Apr 25, 13:55 UTC | 55m |
| 2026-04-24 | CFYSA | - | Apr 24, 18:00 UTC | Apr 24, 19:05 UTC | 1h 5m |
| 2026-04-24 | CFYSA | - | Apr 24, 12:35 UTC | Apr 24, 13:55 UTC | 1h 20m |
| 2026-04-22 | CFYSA | - | Apr 22, 20:00 UTC | Apr 22, 20:35 UTC | 35m |
| 2026-04-22 | CFYSA | - | Apr 22, 18:50 UTC | Apr 22, 19:20 UTC | 30m |
| 2026-04-22 | CFYSA | - | Apr 22, 16:25 UTC | Apr 22, 17:25 UTC | 1h 0m |
| 2026-04-21 | CFYSA | - | Apr 21, 16:01 UTC | Apr 21, 16:50 UTC | 50m |
| 2026-04-21 | CFYSA | - | Apr 21, 13:30 UTC | Apr 21, 14:31 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-FYSA page for operator, model, and routing details .