sensors Mode-S transponder

C03BDF

ICAO 24-bit transponder address · allocated to Canada

Currently assigned to C-FWRM · BEECH 100 King Air · operated by Propair Inc.

Hex
C03BDF
Octal
60035737
Decimal
12,598,239
Country
CA
Tail
C-FWRM
Type
BE10
No current signal · last broadcast 1d ago
Flights observed
101
Distinct callsigns
14
Country
CA
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S C03BDF.

Country allocation

The ICAO 24-bit address C03BDF 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 14 distinct

Callsign Airline Flights Last seen
PRO4700M Propair 26 2026-05-22
PRO4200M - 19 2026-05-27
PRO4245M - 16 2026-05-28
PRO4230M - 7 2026-05-29
PRO4215M - 7 2026-05-30
PRO4150M - 6 2026-05-18
PRO4550 Propair 5 2026-05-13
PRO4701M - 3 2026-05-22
PRO4200 Propair 3 2026-05-24
PRO4165M - 3 2026-05-16
PR04260M - 3 2026-06-01
PRO4130 Propair 1 2026-06-01
PRO1015 Propair 1 2026-06-01
PR04200M - 1 2026-05-31

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-01 PRO4130 YZV → YUL Jun 1, 14:40 UTCJun 1, 15:50 UTC1h 10m
2026-06-01 PRO1015 YUL → YUY Jun 1, 12:20 UTCJun 1, 13:40 UTC1h 20m
2026-06-01 PR04260M - Jun 1, 02:40 UTCJun 1, 03:55 UTC1h 15m
2026-06-01 PR04260M - Jun 1, 00:35 UTCJun 1, 01:20 UTC45m
2026-05-31 PR04260M - May 31, 20:35 UTCMay 31, 20:50 UTC15m
2026-05-31 PR04200M - May 31, 10:05 UTCMay 31, 11:25 UTC1h 20m
2026-05-30 PRO4215M - May 30, 22:05 UTCMay 30, 22:50 UTC45m
2026-05-29 PRO4230M - May 29, 20:35 UTCMay 29, 20:45 UTC10m
2026-05-29 PRO4215M - May 29, 02:55 UTCMay 29, 03:45 UTC50m
2026-05-29 PRO4215M - May 29, 01:20 UTCMay 29, 02:00 UTC40m
2026-05-28 PRO4215M - May 28, 17:50 UTCMay 28, 18:35 UTC45m
2026-05-28 PRO4245M - May 28, 02:15 UTCMay 28, 02:50 UTC35m
2026-05-27 PRO4245M - May 27, 16:10 UTCMay 27, 16:30 UTC20m
2026-05-27 PRO4200M - May 27, 06:04 UTCMay 27, 06:15 UTC10m
2026-05-26 PRO4200M - May 26, 23:39 UTCMay 27, 00:59 UTC1h 20m
2026-05-26 PRO4200M - May 26, 20:54 UTCMay 26, 21:34 UTC40m
2026-05-26 PRO4200M - May 26, 15:14 UTCMay 26, 15:24 UTC10m
2026-05-26 PRO4230M - May 26, 00:24 UTCMay 26, 00:39 UTC15m
2026-05-25 PRO4230M - May 25, 22:15 UTCMay 25, 23:40 UTC1h 25m
2026-05-25 PRO4230M - May 25, 19:50 UTCMay 25, 20:59 UTC1h 10m
2026-05-24 PRO4200 YKU → YUL May 24, 02:40 UTCMay 24, 03:50 UTC1h 10m
2026-05-23 PRO4200 YKU → YUL May 23, 23:45 UTCMay 24, 00:30 UTC45m
2026-05-23 PRO4200 YKU → YUL May 23, 18:20 UTCMay 23, 18:30 UTC10m
2026-05-23 PRO4215M - May 23, 08:15 UTCMay 23, 09:40 UTC1h 25m
2026-05-23 PRO4215M - May 23, 06:45 UTCMay 23, 07:30 UTC45m
2026-05-23 PRO4215M - May 23, 02:55 UTCMay 23, 03:15 UTC20m
2026-05-22 PRO4701M - May 22, 22:10 UTCMay 22, 23:20 UTC1h 10m
2026-05-22 PRO4701M - May 22, 19:10 UTCMay 22, 20:15 UTC1h 5m
2026-05-22 PRO4700M YMT → YUL May 22, 14:25 UTCMay 22, 15:15 UTC50m
2026-05-22 PRO4700M YMT → YUL May 22, 11:40 UTCMay 22, 12:45 UTC1h 5m
2026-05-21 PRO4700M YMT → YUL May 21, 16:25 UTCMay 21, 16:35 UTC10m
2026-05-21 PRO4700M YMT → YUL May 21, 14:55 UTCMay 21, 15:55 UTC1h 0m
2026-05-21 PRO4700M YMT → YUL May 21, 13:10 UTCMay 21, 13:50 UTC40m
2026-05-20 PRO4700M YMT → YUL May 20, 20:15 UTCMay 20, 20:40 UTC25m
2026-05-20 PRO4700M YMT → YUL May 20, 17:50 UTCMay 20, 19:20 UTC1h 30m
2026-05-20 PRO4700M YMT → YUL May 20, 13:50 UTCMay 20, 14:35 UTC45m
2026-05-20 PRO4245M - May 20, 03:40 UTCMay 20, 04:55 UTC1h 16m
2026-05-20 PRO4245M - May 20, 01:50 UTCMay 20, 02:30 UTC40m
2026-05-19 PRO4245M - May 19, 22:50 UTCMay 19, 23:00 UTC10m
2026-05-18 PRO4150M - May 18, 12:15 UTCMay 18, 13:45 UTC1h 30m
2026-05-17 PRO4150M - May 17, 19:40 UTCMay 17, 20:25 UTC45m
2026-05-17 PRO4150M - May 17, 09:15 UTCMay 17, 09:30 UTC15m
2026-05-16 PRO4245M - May 16, 23:50 UTCMay 17, 00:00 UTC10m
2026-05-16 PRO4165M - May 16, 01:20 UTCMay 16, 02:35 UTC1h 15m
2026-05-15 PRO4165M - May 15, 09:15 UTCMay 15, 10:10 UTC55m
2026-05-15 PRO4165M - May 15, 00:20 UTCMay 15, 00:30 UTC10m
2026-05-14 PRO4200M - May 14, 12:40 UTCMay 14, 13:50 UTC1h 10m
2026-05-14 PRO4200M - May 14, 10:25 UTCMay 14, 11:45 UTC1h 20m
2026-05-14 PRO4200M - May 14, 03:20 UTCMay 14, 03:30 UTC10m
2026-05-13 PRO4200M - May 13, 17:20 UTCMay 13, 17:30 UTC10m

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-FWRM page for operator, model, and routing details .

Mode-S C03BDF frequently asked

What is Mode-S code C03BDF?
C03BDF is an ICAO 24-bit transponder address. Allocated to Canada. Assigned to C-FWRM.
Where is Mode-S C03BDF registered?
Mode-S code C03BDF is allocated to Canada (CA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is C03BDF broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex C03BDF, octal 60035737, decimal 12,598,239.
What flights does C03BDF operate?
Mode-S C03BDF has broadcast 14 distinct callsigns, including PRO4700M, PRO4200M, PRO4245M, PRO4230M, PRO4215M.