sensors Mode-S transponder
C013B7
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FHMC · ENSTROM F-28 · operated by 9736140 CANADA INC. (PASCAN AVIATION)
- Hex
- C013B7
- Octal
- 60011667
- Decimal
- 12,587,959
- Country
- CA
- Tail
- C-FHMC
- Type
- EN28
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- CA
- Last broadcast
- 2d ago
Current position
Country allocation
The ICAO 24-bit address C013B7 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PSC484 | Pascan Aviation | 29 | 2026-06-13 |
| PSC373 | - | 29 | 2026-06-12 |
| PSC483 | - | 17 | 2026-06-14 |
| PSC581 | - | 8 | 2026-07-02 |
| PSC381 | - | 6 | 2026-07-10 |
| PSC372 | Pascan Aviation | 6 | 2026-06-14 |
| PSC701 | - | 5 | 2026-07-06 |
| PSC380 | - | 5 | 2026-07-05 |
| PSC951 | Pascan Aviation | 4 | 2026-06-03 |
| PSC801 | Pascan Aviation | 4 | 2026-04-15 |
| PSC723 | Pascan Aviation | 4 | 2026-05-13 |
| PSC702 | - | 4 | 2026-07-09 |
| PSC722 | Pascan Aviation | 3 | 2026-05-07 |
| PSC582 | Pascan Aviation | 3 | 2026-06-04 |
| PSC726 | Pascan Aviation | 2 | 2026-05-15 |
| PSC384 | - | 2 | 2026-07-10 |
| PSC950 | Pascan Aviation | 1 | 2026-05-06 |
| PSC736 | Pascan Aviation | 1 | 2026-04-23 |
| PSC733 | Pascan Aviation | 1 | 2026-04-23 |
| PSC727 | Pascan Aviation | 1 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | PSC378 | - | Jul 11, 20:55 UTC | Jul 11, 22:30 UTC | 1h 35m |
| 2026-07-11 | PSC688 | - | Jul 11, 18:05 UTC | Jul 11, 19:30 UTC | 1h 25m |
| 2026-07-11 | PSC687 | - | Jul 11, 16:20 UTC | Jul 11, 17:35 UTC | 1h 15m |
| 2026-07-11 | PSC375 | - | Jul 11, 12:40 UTC | Jul 11, 14:25 UTC | 1h 45m |
| 2026-07-10 | PSC384 | - | Jul 10, 21:05 UTC | Jul 10, 22:35 UTC | 1h 30m |
| 2026-07-10 | PSC384 | - | Jul 10, 20:45 UTC | Jul 10, 21:00 UTC | 15m |
| 2026-07-10 | PSC381 | - | Jul 10, 13:05 UTC | Jul 10, 14:45 UTC | 1h 40m |
| 2026-07-09 | PSC702 | - | Jul 9, 22:20 UTC | Jul 9, 23:15 UTC | 55m |
| 2026-07-06 | PSC701 | - | Jul 6, 10:40 UTC | Jul 6, 11:55 UTC | 1h 15m |
| 2026-07-05 | PSC380 | - | Jul 5, 17:30 UTC | Jul 5, 19:10 UTC | 1h 40m |
| 2026-07-05 | PSC381 | - | Jul 5, 14:35 UTC | Jul 5, 16:10 UTC | 1h 35m |
| 2026-07-02 | PSC581 | - | Jul 2, 09:45 UTC | Jul 2, 12:05 UTC | 2h 20m |
| 2026-07-01 | PSC581 | - | Jul 1, 21:50 UTC | Jul 2, 00:20 UTC | 2h 30m |
| 2026-06-25 | PSC702 | YWK → YQB | Jun 25, 22:20 UTC | Jun 25, 23:34 UTC | 1h 15m |
| 2026-06-22 | PSC701 | - | Jun 22, 10:30 UTC | Jun 22, 11:54 UTC | 1h 25m |
| 2026-06-18 | PSC702 | YWK → YQB | Jun 18, 22:30 UTC | Jun 18, 23:50 UTC | 1h 20m |
| 2026-06-15 | PSC701 | YHU → YQB | Jun 15, 10:35 UTC | Jun 15, 11:49 UTC | 1h 15m |
| 2026-06-14 | PSC372 | YVB → YHU | Jun 14, 18:30 UTC | Jun 14, 20:45 UTC | 2h 15m |
| 2026-06-14 | PSC483 | - | Jun 14, 15:05 UTC | Jun 14, 16:10 UTC | 1h 5m |
| 2026-06-14 | PSC483 | YHU → YQB | Jun 14, 13:35 UTC | Jun 14, 14:10 UTC | 35m |
| 2026-06-13 | PSC484 | YQB → YHU | Jun 13, 01:25 UTC | Jun 13, 04:00 UTC | 2h 34m |
| 2026-06-12 | PSC373 | - | Jun 12, 21:10 UTC | Jun 12, 23:25 UTC | 2h 15m |
| 2026-06-11 | PSC702 | YWK → YQB | Jun 11, 22:15 UTC | Jun 11, 23:15 UTC | 1h 0m |
| 2026-06-08 | PSC701 | YHU → YQB | Jun 8, 11:35 UTC | Jun 8, 11:55 UTC | 20m |
| 2026-06-08 | PSC701 | YHU → YQB | Jun 8, 10:25 UTC | Jun 8, 11:00 UTC | 35m |
| 2026-06-04 | PSC582 | YQB → YHU | Jun 4, 09:55 UTC | Jun 4, 12:10 UTC | 2h 15m |
| 2026-06-03 | PSC581 | YHU → YQB | Jun 3, 23:45 UTC | Jun 4, 01:00 UTC | 1h 15m |
| 2026-06-03 | PSC581 | YHU → YQB | Jun 3, 22:15 UTC | Jun 3, 22:55 UTC | 40m |
| 2026-06-03 | PSC951 | YHU → YSJ | Jun 3, 18:15 UTC | Jun 3, 20:15 UTC | 2h 0m |
| 2026-06-03 | PSC951 | YHU → YSJ | Jun 3, 13:15 UTC | Jun 3, 15:25 UTC | 2h 10m |
| 2026-06-02 | PSC201 | - | Jun 2, 17:10 UTC | Jun 2, 17:55 UTC | 45m |
| 2026-05-27 | PSC582 | YQB → YHU | May 27, 10:00 UTC | May 27, 12:25 UTC | 2h 25m |
| 2026-05-26 | PSC581 | YHU → YQB | May 26, 23:39 UTC | May 27, 01:05 UTC | 1h 25m |
| 2026-05-26 | PSC581 | YHU → YQB | May 26, 21:09 UTC | May 26, 21:40 UTC | 30m |
| 2026-05-20 | PSC484 | YQB → YHU | May 20, 21:30 UTC | May 20, 22:50 UTC | 1h 20m |
| 2026-05-20 | PSC484 | YQB → YHU | May 20, 20:30 UTC | May 20, 20:55 UTC | 25m |
| 2026-05-20 | PSC373 | YHU → YVB | May 20, 15:45 UTC | May 20, 17:45 UTC | 2h 0m |
| 2026-05-20 | PSC582 | YQB → YHU | May 20, 10:35 UTC | May 20, 12:55 UTC | 2h 20m |
| 2026-05-19 | PSC581 | YHU → YQB | May 19, 23:10 UTC | May 20, 00:20 UTC | 1h 10m |
| 2026-05-19 | PSC581 | YHU → YQB | May 19, 21:35 UTC | May 19, 22:10 UTC | 35m |
| 2026-05-18 | PSC484 | YQB → YHU | May 18, 21:20 UTC | May 18, 22:55 UTC | 1h 35m |
| 2026-05-18 | PSC484 | YQB → YHU | May 18, 20:30 UTC | May 18, 20:50 UTC | 20m |
| 2026-05-18 | PSC373 | YHU → YVB | May 18, 15:30 UTC | May 18, 17:40 UTC | 2h 10m |
| 2026-05-17 | PSC484 | YQB → YHU | May 17, 21:35 UTC | May 17, 22:45 UTC | 1h 10m |
| 2026-05-17 | PSC484 | YQB → YHU | May 17, 20:35 UTC | May 17, 20:55 UTC | 20m |
| 2026-05-17 | PSC373 | YHU → YVB | May 17, 17:35 UTC | May 17, 17:50 UTC | 15m |
| 2026-05-17 | PSC373 | YHU → YVB | May 17, 15:40 UTC | May 17, 17:10 UTC | 1h 30m |
| 2026-05-15 | PSC372 | YVB → YHU | May 15, 18:55 UTC | May 15, 20:25 UTC | 1h 30m |
| 2026-05-15 | PSC372 | YVB → YHU | May 15, 18:05 UTC | May 15, 18:15 UTC | 10m |
| 2026-05-15 | PSC483 | YHU → YQB | May 15, 14:20 UTC | May 15, 15:30 UTC | 1h 9m |
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-FHMC page for operator, model, and routing details .