sensors Mode-S transponder
C00558
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FCAP · CESSNA 172 Skyhawk · operated by Pacific Flying Club
- Hex
- C00558
- Octal
- 60002530
- Decimal
- 12,584,280
- Country
- CA
- Tail
- C-FCAP
- Type
- C172
- Flights observed
- 76
- Distinct callsigns
- 1
- Country
- CA
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address C00558 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 |
|---|---|---|---|
| CFCAP | - | 76 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | CFCAP | - | Jul 15, 03:00 UTC | Jul 15, 04:20 UTC | 1h 20m |
| 2026-07-15 | CFCAP | - | Jul 15, 00:25 UTC | Jul 15, 01:30 UTC | 1h 5m |
| 2026-07-13 | CFCAP | YDT → YDT | Jul 13, 21:35 UTC | Jul 13, 22:35 UTC | 1h 0m |
| 2026-07-08 | CFCAP | YDT → YDT | Jul 8, 23:50 UTC | Jul 9, 01:55 UTC | 2h 5m |
| 2026-06-24 | CFCAP | YDT → YDT | Jun 24, 00:20 UTC | Jun 24, 01:24 UTC | 1h 5m |
| 2026-06-21 | CFCAP | - | Jun 21, 19:39 UTC | Jun 21, 20:59 UTC | 1h 20m |
| 2026-06-19 | CFCAP | - | Jun 19, 04:00 UTC | Jun 19, 06:20 UTC | 2h 20m |
| 2026-06-19 | CFCAP | - | Jun 19, 02:45 UTC | Jun 19, 03:15 UTC | 30m |
| 2026-06-19 | CFCAP | - | Jun 19, 00:29 UTC | Jun 19, 01:15 UTC | 45m |
| 2026-06-15 | CFCAP | - | Jun 15, 22:00 UTC | Jun 15, 22:25 UTC | 25m |
| 2026-06-15 | CFCAP | - | Jun 15, 19:55 UTC | Jun 15, 20:04 UTC | 10m |
| 2026-06-15 | CFCAP | - | Jun 15, 18:40 UTC | Jun 15, 19:25 UTC | 45m |
| 2026-06-14 | CFCAP | - | Jun 14, 03:10 UTC | Jun 14, 03:45 UTC | 35m |
| 2026-06-13 | CFCAP | - | Jun 13, 23:00 UTC | Jun 13, 23:45 UTC | 45m |
| 2026-06-13 | CFCAP | - | Jun 13, 21:00 UTC | Jun 13, 21:45 UTC | 45m |
| 2026-06-13 | CFCAP | - | Jun 13, 16:20 UTC | Jun 13, 16:45 UTC | 25m |
| 2026-06-13 | CFCAP | - | Jun 13, 00:40 UTC | Jun 13, 03:20 UTC | 2h 40m |
| 2026-06-12 | CFCAP | - | Jun 12, 21:00 UTC | Jun 12, 23:40 UTC | 2h 40m |
| 2026-06-11 | CFCAP | - | Jun 11, 23:55 UTC | Jun 12, 02:00 UTC | 2h 6m |
| 2026-06-11 | CFCAP | - | Jun 11, 20:05 UTC | Jun 11, 20:45 UTC | 40m |
| 2026-06-03 | CFCAP | - | Jun 3, 02:30 UTC | Jun 3, 05:05 UTC | 2h 35m |
| 2026-06-02 | CFCAP | - | Jun 2, 23:35 UTC | Jun 3, 01:30 UTC | 1h 55m |
| 2026-06-02 | CFCAP | - | Jun 2, 22:00 UTC | Jun 2, 22:25 UTC | 25m |
| 2026-06-02 | CFCAP | - | Jun 2, 03:00 UTC | Jun 2, 06:10 UTC | 3h 10m |
| 2026-05-31 | CFCAP | - | May 31, 22:30 UTC | Jun 1, 01:15 UTC | 2h 45m |
| 2026-05-31 | CFCAP | - | May 31, 20:00 UTC | May 31, 21:25 UTC | 1h 25m |
| 2026-05-31 | CFCAP | YDT → YBL | May 31, 17:50 UTC | May 31, 19:10 UTC | 1h 20m |
| 2026-05-28 | CFCAP | - | May 28, 03:55 UTC | May 28, 10:05 UTC | 6h 10m |
| 2026-05-28 | CFCAP | - | May 28, 01:10 UTC | May 28, 01:35 UTC | 25m |
| 2026-05-27 | CFCAP | - | May 27, 18:05 UTC | May 27, 18:45 UTC | 40m |
| 2026-05-21 | CFCAP | - | May 21, 08:05 UTC | May 21, 09:35 UTC | 1h 30m |
| 2026-05-21 | CFCAP | - | May 21, 06:05 UTC | May 21, 07:25 UTC | 1h 20m |
| 2026-05-18 | CFCAP | YDT → YDT | May 18, 21:40 UTC | May 18, 23:00 UTC | 1h 20m |
| 2026-05-12 | CFCAP | - | May 12, 08:00 UTC | May 12, 11:15 UTC | 3h 15m |
| 2026-05-12 | CFCAP | - | May 12, 04:00 UTC | May 12, 07:25 UTC | 3h 25m |
| 2026-05-11 | CFCAP | - | May 11, 21:20 UTC | May 11, 21:50 UTC | 30m |
| 2026-05-11 | CFCAP | - | May 11, 19:45 UTC | May 11, 20:35 UTC | 50m |
| 2026-05-11 | CFCAP | - | May 11, 01:25 UTC | May 11, 02:00 UTC | 35m |
| 2026-05-09 | CFCAP | - | May 9, 20:15 UTC | May 9, 20:49 UTC | 35m |
| 2026-05-06 | CFCAP | YDT → YDT | May 6, 04:15 UTC | May 6, 09:10 UTC | 4h 55m |
| 2026-05-05 | CFCAP | - | May 5, 02:45 UTC | May 5, 03:15 UTC | 30m |
| 2026-05-05 | CFCAP | - | May 5, 00:40 UTC | May 5, 01:30 UTC | 50m |
| 2026-05-04 | CFCAP | - | May 4, 21:05 UTC | May 4, 23:20 UTC | 2h 15m |
| 2026-05-02 | CFCAP | YBL → YDT | May 2, 06:50 UTC | May 2, 08:40 UTC | 1h 50m |
| 2026-05-02 | CFCAP | - | May 2, 04:15 UTC | May 2, 06:15 UTC | 2h 0m |
| 2026-05-01 | CFCAP | - | May 1, 09:25 UTC | May 1, 09:45 UTC | 20m |
| 2026-05-01 | CFCAP | - | May 1, 05:25 UTC | May 1, 08:50 UTC | 3h 25m |
| 2026-05-01 | CFCAP | - | May 1, 04:25 UTC | May 1, 04:50 UTC | 25m |
| 2026-05-01 | CFCAP | - | May 1, 01:15 UTC | May 1, 01:40 UTC | 25m |
| 2026-04-30 | CFCAP | - | Apr 30, 20:45 UTC | Apr 30, 21:10 UTC | 25m |
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-FCAP page for operator, model, and routing details .