Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

7C4A09

ICAO 24-bit transponder address · allocated to Australia

Currently assigned to VH-OWR · PILATUS PC-12 · operated by ROYAL FLYING DOCTOR SERVICE OF AUSTRALIA (WESTERN OPERATIONS)

Hex
7C4A09
Octal
37045011
Decimal
8,145,417
Country
AU
Tail
VH-OWR
Type
PC12
No current signal · last broadcast 58m ago
Flights observed
107
Distinct callsigns
1
Country
AU
Last broadcast
58m ago

Last known position

Most recent position reported by Mode-S 7C4A09.

Country allocation

The ICAO 24-bit address 7C4A09 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 1 distinct

Callsign Airline Flights Last seen
FD613 Thai AirAsia 107 2026-06-02

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 FD613 SAI → HKT Jun 2, 17:10 UTCJun 2, 18:15 UTC1h 5m
2026-06-02 FD613 SAI → HKT Jun 2, 15:55 UTCJun 2, 16:25 UTC30m
2026-06-02 FD613 SAI → HKT Jun 2, 14:50 UTCJun 2, 15:15 UTC25m
2026-06-02 FD613 SAI → HKT Jun 2, 13:20 UTCJun 2, 13:50 UTC30m
2026-06-02 FD613 SAI → HKT Jun 2, 10:40 UTCJun 2, 10:55 UTC15m
2026-06-02 FD613 SAI → HKT Jun 2, 09:30 UTCJun 2, 09:45 UTC15m
2026-06-02 FD613 SAI → HKT Jun 2, 06:15 UTCJun 2, 06:40 UTC25m
2026-06-02 FD613 SAI → HKT Jun 2, 03:35 UTCJun 2, 04:50 UTC1h 15m
2026-06-02 FD613 SAI → HKT Jun 2, 01:50 UTCJun 2, 02:30 UTC40m
2026-06-02 FD613 SAI → HKT Jun 2, 00:55 UTCJun 2, 01:15 UTC20m
2026-06-01 FD613 SAI → HKT Jun 1, 08:30 UTCJun 1, 08:50 UTC20m
2026-06-01 FD613 SAI → HKT Jun 1, 04:45 UTCJun 1, 05:05 UTC20m
2026-05-30 FD613 SAI → HKT May 30, 04:15 UTCMay 30, 04:25 UTC10m
2026-05-30 FD613 SAI → HKT May 30, 02:10 UTCMay 30, 02:20 UTC10m
2026-05-30 FD613 SAI → HKT May 30, 01:20 UTCMay 30, 01:30 UTC10m
2026-05-29 FD613 SAI → HKT May 29, 23:10 UTCMay 29, 23:30 UTC20m
2026-05-29 FD613 SAI → HKT May 29, 07:55 UTCMay 29, 09:00 UTC1h 5m
2026-05-29 FD613 SAI → HKT May 29, 05:30 UTCMay 29, 06:05 UTC35m
2026-05-29 FD613 SAI → HKT May 29, 04:35 UTCMay 29, 04:50 UTC15m
2026-05-28 FD613 SAI → HKT May 28, 17:35 UTCMay 28, 17:45 UTC10m
2026-05-28 FD613 SAI → HKT May 28, 14:10 UTCMay 28, 14:50 UTC40m
2026-05-28 FD613 SAI → HKT May 28, 11:50 UTCMay 28, 13:15 UTC1h 25m
2026-05-28 FD613 SAI → HKT May 28, 10:10 UTCMay 28, 10:20 UTC10m
2026-05-28 FD613 SAI → HKT May 28, 07:35 UTCMay 28, 07:45 UTC10m
2026-05-27 FD613 SAI → HKT May 27, 06:25 UTCMay 27, 07:45 UTC1h 20m
2026-05-27 FD613 SAI → HKT May 27, 04:14 UTCMay 27, 05:09 UTC55m
2026-05-27 FD613 SAI → HKT May 27, 01:14 UTCMay 27, 01:24 UTC10m
2026-05-26 FD613 SAI → HKT May 26, 19:50 UTCMay 26, 20:05 UTC15m
2026-05-26 FD613 SAI → HKT May 26, 17:50 UTCMay 26, 18:05 UTC15m
2026-05-26 FD613 SAI → HKT May 26, 15:09 UTCMay 26, 15:24 UTC15m
2026-05-26 FD613 SAI → HKT May 26, 12:40 UTCMay 26, 13:00 UTC20m
2026-05-26 FD613 SAI → HKT May 26, 11:44 UTCMay 26, 11:54 UTC10m
2026-05-26 FD613 SAI → HKT May 26, 07:40 UTCMay 26, 07:55 UTC15m
2026-05-24 FD613 SAI → HKT May 24, 07:05 UTCMay 24, 08:20 UTC1h 15m
2026-05-24 FD613 SAI → HKT May 24, 03:30 UTCMay 24, 04:00 UTC30m
2026-05-24 FD613 SAI → HKT May 24, 02:35 UTCMay 24, 02:50 UTC15m
2026-05-23 FD613 SAI → HKT May 23, 18:20 UTCMay 23, 19:35 UTC1h 15m
2026-05-23 FD613 SAI → HKT May 23, 17:25 UTCMay 23, 17:55 UTC30m
2026-05-23 FD613 SAI → HKT May 23, 15:45 UTCMay 23, 16:10 UTC25m
2026-05-23 FD613 SAI → HKT May 23, 08:35 UTCMay 23, 08:45 UTC10m
2026-05-23 FD613 SAI → HKT May 23, 05:55 UTCMay 23, 07:10 UTC1h 15m
2026-05-19 FD613 SAI → HKT May 19, 02:35 UTCMay 19, 02:45 UTC10m
2026-05-18 FD613 SAI → HKT May 18, 05:35 UTCMay 18, 06:05 UTC30m
2026-05-18 FD613 SAI → HKT May 18, 05:05 UTCMay 18, 05:15 UTC10m
2026-05-18 FD613 SAI → HKT May 18, 03:55 UTCMay 18, 05:00 UTC1h 5m
2026-05-15 FD613 SAI → HKT May 15, 11:50 UTCMay 15, 12:10 UTC20m
2026-05-15 FD613 SAI → HKT May 15, 06:35 UTCMay 15, 08:20 UTC1h 45m
2026-05-14 FD613 SAI → HKT May 14, 06:25 UTCMay 14, 07:20 UTC55m
2026-05-14 FD613 SAI → HKT May 14, 02:55 UTCMay 14, 03:40 UTC45m
2026-05-13 FD613 SAI → HKT May 13, 15:00 UTCMay 13, 15:35 UTC35m

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

Mode-S 7C4A09 frequently asked

What is Mode-S code 7C4A09?
7C4A09 is an ICAO 24-bit transponder address. Allocated to Australia. Assigned to VH-OWR.
Where is Mode-S 7C4A09 registered?
Mode-S code 7C4A09 is allocated to Australia (AU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 7C4A09 broadcasting right now?
No active broadcast right now. Last signal was 58m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 7C4A09, octal 37045011, decimal 8,145,417.
What flights does 7C4A09 operate?
Mode-S 7C4A09 has broadcast 1 distinct callsign, including FD613.