sensors Mode-S transponder
C0203F
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FMFM · CESSNA 550 Citation S2 · operated by BEAVER AIR SERVICES LIMITED PARTNERSHIP, BY ITS GENERAL PARTNER, MISSINIPPI MANAGEMENT LTD.
- Hex
- C0203F
- Octal
- 60020077
- Decimal
- 12,591,167
- Country
- CA
- Tail
- C-FMFM
- Type
- C550
- Flights observed
- 46
- Distinct callsigns
- 2
- Country
- CA
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address C0203F 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 2 distinct
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | MCB702 | - | Jul 3, 14:10 UTC | Jul 3, 17:15 UTC | 3h 5m |
| 2026-07-03 | MCB702 | YWG → FAR | Jul 3, 12:50 UTC | Jul 3, 13:35 UTC | 45m |
| 2026-07-02 | MCB702 | - | Jul 2, 09:45 UTC | Jul 2, 14:10 UTC | 4h 25m |
| 2026-07-01 | MCB702 | YWG → YWG | Jul 1, 12:35 UTC | Jul 1, 17:00 UTC | 4h 25m |
| 2026-07-01 | MCB702 | - | Jul 1, 07:50 UTC | Jul 1, 08:30 UTC | 40m |
| 2026-06-30 | MCB702 | YWG → YWG | Jun 30, 12:00 UTC | Jul 1, 08:30 UTC | 20h 30m |
| 2026-06-28 | MCB702 | - | Jun 28, 23:39 UTC | Jun 29, 03:14 UTC | 3h 35m |
| 2026-06-28 | MCB702 | - | Jun 28, 20:34 UTC | Jun 28, 22:39 UTC | 2h 5m |
| 2026-06-28 | MCB702 | - | Jun 28, 15:34 UTC | Jun 28, 19:14 UTC | 3h 40m |
| 2026-06-27 | MCB702 | YRT → YWG | Jun 27, 18:49 UTC | Jun 28, 02:49 UTC | 8h 0m |
| 2026-06-27 | MCB702 | - | Jun 27, 17:20 UTC | Jun 27, 17:34 UTC | 15m |
| 2026-06-26 | MCB009 | - | Jun 26, 00:15 UTC | Jun 26, 00:50 UTC | 35m |
| 2026-06-25 | MCB009 | - | Jun 25, 20:59 UTC | Jun 25, 21:35 UTC | 35m |
| 2026-06-25 | MCB009 | YWG → YWG | Jun 25, 13:55 UTC | Jun 25, 17:54 UTC | 4h 0m |
| 2026-06-23 | MCB009 | YWG → YWG | Jun 23, 11:19 UTC | Jun 23, 20:54 UTC | 9h 35m |
| 2026-06-22 | MCB702 | YWG → YWG | Jun 22, 18:30 UTC | Jun 22, 22:19 UTC | 3h 50m |
| 2026-06-22 | MCB702 | - | Jun 22, 11:09 UTC | Jun 22, 14:59 UTC | 3h 50m |
| 2026-06-19 | MCB702 | - | Jun 19, 21:19 UTC | Jun 20, 00:59 UTC | 3h 40m |
| 2026-06-10 | MCB702 | - | Jun 10, 20:45 UTC | Jun 11, 00:05 UTC | 3h 20m |
| 2026-06-10 | MCB702 | - | Jun 10, 15:55 UTC | Jun 10, 19:20 UTC | 3h 25m |
| 2026-06-09 | MCB702 | YWG → YWG | Jun 9, 17:25 UTC | Jun 9, 18:10 UTC | 45m |
| 2026-06-08 | MCB702 | YWG → YWG | Jun 8, 15:25 UTC | Jun 8, 16:45 UTC | 1h 20m |
| 2026-06-07 | MCB702 | YWG → YWG | Jun 7, 15:20 UTC | Jun 7, 18:15 UTC | 2h 55m |
| 2026-05-08 | MCB702 | - | May 8, 19:20 UTC | May 8, 20:00 UTC | 40m |
| 2026-05-08 | MCB702 | - | May 8, 15:55 UTC | May 8, 16:30 UTC | 35m |
| 2026-05-07 | MCB702 | YWG → YWG | May 7, 21:30 UTC | May 8, 01:04 UTC | 3h 35m |
| 2026-05-07 | MCB702 | YWG → YWG | May 7, 13:50 UTC | May 7, 17:55 UTC | 4h 5m |
| 2026-05-06 | MCB702 | YWG → YWG | May 6, 15:45 UTC | May 6, 22:00 UTC | 6h 15m |
| 2026-04-26 | MCB702 | YWG → YWG | Apr 26, 19:55 UTC | Apr 27, 01:05 UTC | 5h 10m |
| 2026-04-26 | MCB702 | YWG → YWG | Apr 26, 15:20 UTC | Apr 26, 19:10 UTC | 3h 50m |
| 2026-04-25 | MCB702 | YWG → YWG | Apr 25, 18:55 UTC | Apr 25, 22:55 UTC | 4h 0m |
| 2026-04-23 | MCB702 | YWG → YWG | Apr 23, 15:40 UTC | Apr 23, 23:50 UTC | 8h 10m |
| 2026-04-20 | MCB702 | - | Apr 20, 20:55 UTC | Apr 20, 21:30 UTC | 35m |
| 2026-04-20 | MCB702 | - | Apr 20, 15:45 UTC | Apr 20, 16:35 UTC | 50m |
| 2026-04-17 | MCB702 | - | Apr 17, 18:20 UTC | Apr 17, 19:10 UTC | 50m |
| 2026-04-17 | MCB702 | - | Apr 17, 15:20 UTC | Apr 17, 15:35 UTC | 15m |
| 2026-04-17 | MCB702 | - | Apr 17, 15:00 UTC | Apr 17, 15:15 UTC | 15m |
| 2026-04-16 | MCB702 | - | Apr 16, 23:20 UTC | Apr 16, 23:40 UTC | 20m |
| 2026-04-16 | MCB702 | - | Apr 16, 23:00 UTC | Apr 16, 23:10 UTC | 10m |
| 2026-04-16 | MCB702 | - | Apr 16, 19:35 UTC | Apr 16, 20:20 UTC | 45m |
| 2026-04-16 | MCB702 | - | Apr 16, 01:25 UTC | Apr 16, 02:04 UTC | 40m |
| 2026-04-15 | MCB702 | - | Apr 15, 21:20 UTC | Apr 15, 22:05 UTC | 45m |
| 2026-04-15 | MCB702 | - | Apr 15, 00:05 UTC | Apr 15, 00:40 UTC | 35m |
| 2026-04-14 | MCB702 | - | Apr 14, 16:15 UTC | Apr 14, 16:45 UTC | 30m |
| 2026-04-13 | MCB702 | - | Apr 13, 00:20 UTC | Apr 13, 00:40 UTC | 20m |
| 2026-04-13 | MCB702 | - | Apr 13, 00:00 UTC | Apr 13, 00:40 UTC | 40m |
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-FMFM page for operator, model, and routing details .