Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

7C1C45

ICAO 24-bit transponder address · allocated to Australia

Currently assigned to VH-FVB · PILATUS PC-12 · operated by ROYAL FLYING DOCTOR SERVICE OF AUSTRALIA CENTRAL OPERATIONS

Hex
7C1C45
Octal
37016105
Decimal
8,133,701
Country
AU
Tail
VH-FVB
Type
PC12
Broadcasting now · callsign FD539 · 15,950 ft
Flights observed
268
Distinct callsigns
20
Country
AU
Last broadcast
4h ago

Current position

7C1C45 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 7C1C45 falls within the block assigned to Australia (AU) by ICAO Annex 10, Volume III. Every aircraft registered in Australia 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
FD533 Thai AirAsia 19 2026-05-29
FD513 Thai AirAsia 18 2026-05-26
FD540 - 17 2026-05-29
FD532 Thai AirAsia 17 2026-06-02
FD516 Thai AirAsia 17 2026-05-31
FD580 - 16 2026-05-29
FD575 - 14 2026-05-22
FD524 - 13 2026-05-21
FD519 Thai AirAsia 13 2026-06-01
FD518 Thai AirAsia 12 2026-05-27
FD522 - 11 2026-06-01
FD517 Thai AirAsia 10 2026-06-03
FD514 - 10 2026-05-30
FD567 Thai AirAsia 9 2026-05-19
FD542 - 9 2026-05-23
FD534 - 9 2026-05-13
FD526 - 9 2026-05-30
FD531 Thai AirAsia 8 2026-05-26
FD549 - 6 2026-06-02
FD527 - 6 2026-05-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-03 FD517 HKG → DMK Jun 3, 06:20 UTCJun 3, 06:45 UTC25m
2026-06-03 FD517 HKG → DMK Jun 3, 05:20 UTCJun 3, 05:45 UTC25m
2026-06-03 FD517 HKG → DMK Jun 3, 00:15 UTCJun 3, 01:35 UTC1h 20m
2026-06-02 FD549 - Jun 2, 18:35 UTCJun 2, 19:05 UTC30m
2026-06-02 FD549 - Jun 2, 15:10 UTCJun 2, 16:05 UTC55m
2026-06-02 FD549 - Jun 2, 12:50 UTCJun 2, 13:30 UTC40m
2026-06-02 FD549 - Jun 2, 11:20 UTCJun 2, 11:50 UTC30m
2026-06-02 FD532 DMK → CAN Jun 2, 06:15 UTCJun 2, 07:15 UTC1h 0m
2026-06-02 FD532 DMK → CAN Jun 2, 04:00 UTCJun 2, 04:50 UTC50m
2026-06-02 FD532 DMK → CAN Jun 2, 01:35 UTCJun 2, 02:20 UTC45m
2026-06-02 FD532 DMK → CAN Jun 2, 00:15 UTCJun 2, 01:00 UTC45m
2026-06-01 FD532 DMK → CAN Jun 1, 23:05 UTCJun 1, 23:30 UTC25m
2026-06-01 FD522 - Jun 1, 15:00 UTCJun 1, 15:30 UTC30m
2026-06-01 FD522 - Jun 1, 13:25 UTCJun 1, 13:35 UTC10m
2026-06-01 FD522 - Jun 1, 10:45 UTCJun 1, 11:35 UTC50m
2026-06-01 FD519 OKA → HKG Jun 1, 08:55 UTCJun 1, 09:20 UTC25m
2026-06-01 FD519 OKA → HKG Jun 1, 07:45 UTCJun 1, 08:00 UTC15m
2026-06-01 FD519 OKA → HKG Jun 1, 06:15 UTCJun 1, 06:25 UTC10m
2026-06-01 FD519 OKA → HKG Jun 1, 04:55 UTCJun 1, 05:20 UTC25m
2026-06-01 FD519 OKA → HKG Jun 1, 03:10 UTCJun 1, 03:55 UTC45m
2026-05-31 FD516 HKG → CNX May 31, 18:05 UTCMay 31, 18:40 UTC35m
2026-05-31 FD516 HKG → CNX May 31, 17:00 UTCMay 31, 17:20 UTC20m
2026-05-31 FD516 HKG → CNX May 31, 15:10 UTCMay 31, 16:10 UTC1h 0m
2026-05-31 FD516 HKG → CNX May 31, 14:10 UTCMay 31, 14:40 UTC30m
2026-05-31 FD516 HKG → CNX May 31, 12:45 UTCMay 31, 13:10 UTC25m
2026-05-31 FD516 HKG → CNX May 31, 10:45 UTCMay 31, 11:05 UTC20m
2026-05-31 FD521 - May 31, 00:25 UTCMay 31, 00:55 UTC30m
2026-05-30 FD521 - May 30, 22:45 UTCMay 30, 23:05 UTC20m
2026-05-30 FD514 - May 30, 20:30 UTCMay 30, 21:30 UTC1h 0m
2026-05-30 FD514 - May 30, 18:35 UTCMay 30, 19:30 UTC55m
2026-05-30 FD514 - May 30, 16:55 UTCMay 30, 17:35 UTC40m
2026-05-30 FD514 - May 30, 13:50 UTCMay 30, 14:20 UTC30m
2026-05-30 FD516 HKG → CNX May 30, 11:55 UTCMay 30, 12:20 UTC25m
2026-05-30 FD516 HKG → CNX May 30, 10:55 UTCMay 30, 11:15 UTC20m
2026-05-30 FD516 HKG → CNX May 30, 09:55 UTCMay 30, 10:20 UTC25m
2026-05-30 FD516 HKG → CNX May 30, 08:10 UTCMay 30, 08:30 UTC20m
2026-05-30 FD516 HKG → CNX May 30, 07:45 UTCMay 30, 07:50 UTC5m
2026-05-30 FD516 HKG → CNX May 30, 05:45 UTCMay 30, 06:30 UTC45m
2026-05-30 FD526 - May 30, 03:40 UTCMay 30, 04:15 UTC35m
2026-05-30 FD526 - May 30, 01:05 UTCMay 30, 01:35 UTC30m
2026-05-29 FD549 - May 29, 22:50 UTCMay 29, 23:15 UTC25m
2026-05-29 FD549 - May 29, 21:20 UTCMay 29, 21:45 UTC25m
2026-05-29 FD540 - May 29, 19:05 UTCMay 29, 19:35 UTC30m
2026-05-29 FD540 - May 29, 14:05 UTCMay 29, 14:30 UTC25m
2026-05-29 FD533 CAN → DMK May 29, 12:40 UTCMay 29, 13:10 UTC30m
2026-05-29 FD533 CAN → DMK May 29, 09:10 UTCMay 29, 10:00 UTC50m
2026-05-29 FD533 CAN → DMK May 29, 07:35 UTCMay 29, 07:55 UTC20m
2026-05-29 FD533 CAN → DMK May 29, 06:40 UTCMay 29, 07:00 UTC20m
2026-05-29 FD580 - May 29, 04:50 UTCMay 29, 05:05 UTC15m
2026-05-29 FD580 - May 29, 03:55 UTCMay 29, 04:15 UTC20m

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

Mode-S 7C1C45 frequently asked

What is Mode-S code 7C1C45?
7C1C45 is an ICAO 24-bit transponder address. Allocated to Australia. Assigned to VH-FVB.
Where is Mode-S 7C1C45 registered?
Mode-S code 7C1C45 is allocated to Australia (AU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 7C1C45 broadcasting right now?
Yes. Mode-S 7C1C45 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 7C1C45, octal 37016105, decimal 8,133,701.
What flights does 7C1C45 operate?
Mode-S 7C1C45 has broadcast 20 distinct callsigns, including FD533, FD513, FD540, FD532, FD516.