sensors Mode-S transponder
7C49FE
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-OWG · PILATUS PC-12 · operated by ROYAL FLYING DOCTOR SERVICE OF AUSTRALIA (WESTERN OPERATIONS)
- Hex
- 7C49FE
- Octal
- 37044776
- Decimal
- 8,145,406
- Country
- AU
- Tail
- VH-OWG
- Type
- PC12
- Flights observed
- 116
- Distinct callsigns
- 1
- Country
- AU
- Last broadcast
- Jun 9, 06:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 7C49FE 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 |
|---|---|---|---|
| FD604 | - | 116 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | FD604 | - | Jun 9, 06:10 UTC | Jun 9, 06:40 UTC | 30m |
| 2026-06-09 | FD604 | - | Jun 9, 02:25 UTC | Jun 9, 03:00 UTC | 35m |
| 2026-06-08 | FD604 | - | Jun 8, 17:30 UTC | Jun 8, 18:10 UTC | 40m |
| 2026-06-08 | FD604 | - | Jun 8, 16:10 UTC | Jun 8, 16:35 UTC | 25m |
| 2026-06-08 | FD604 | - | Jun 8, 14:00 UTC | Jun 8, 14:55 UTC | 55m |
| 2026-06-08 | FD604 | - | Jun 8, 13:05 UTC | Jun 8, 13:25 UTC | 20m |
| 2026-06-08 | FD604 | JAD → KGI | Jun 8, 11:15 UTC | Jun 8, 12:30 UTC | 1h 15m |
| 2026-06-08 | FD604 | - | Jun 8, 06:25 UTC | Jun 8, 07:15 UTC | 50m |
| 2026-06-08 | FD604 | - | Jun 8, 03:30 UTC | Jun 8, 04:20 UTC | 50m |
| 2026-06-07 | FD604 | - | Jun 7, 17:50 UTC | Jun 7, 18:35 UTC | 45m |
| 2026-06-07 | FD604 | - | Jun 7, 14:00 UTC | Jun 7, 14:50 UTC | 50m |
| 2026-06-06 | FD604 | BQB → JAD | Jun 6, 11:00 UTC | Jun 6, 11:35 UTC | 35m |
| 2026-06-06 | FD604 | - | Jun 6, 09:55 UTC | Jun 6, 10:25 UTC | 30m |
| 2026-06-06 | FD604 | - | Jun 6, 08:40 UTC | Jun 6, 09:19 UTC | 40m |
| 2026-06-06 | FD604 | - | Jun 6, 07:35 UTC | Jun 6, 08:05 UTC | 30m |
| 2026-06-06 | FD604 | - | Jun 6, 05:30 UTC | Jun 6, 06:05 UTC | 35m |
| 2026-06-06 | FD604 | - | Jun 6, 03:45 UTC | Jun 6, 04:25 UTC | 40m |
| 2026-06-06 | FD604 | BQB → JAD | Jun 6, 01:45 UTC | Jun 6, 02:20 UTC | 35m |
| 2026-06-06 | FD604 | JAD → BQB | Jun 6, 00:25 UTC | Jun 6, 01:00 UTC | 35m |
| 2026-06-05 | FD604 | JAD → JAD | Jun 5, 22:20 UTC | Jun 5, 23:40 UTC | 1h 20m |
| 2026-06-05 | FD604 | - | Jun 5, 19:45 UTC | Jun 5, 20:25 UTC | 40m |
| 2026-06-05 | FD604 | - | Jun 5, 16:20 UTC | Jun 5, 17:10 UTC | 50m |
| 2026-06-05 | FD604 | BQB → JAD | Jun 5, 14:25 UTC | Jun 5, 14:55 UTC | 30m |
| 2026-06-05 | FD604 | - | Jun 5, 13:40 UTC | Jun 5, 13:50 UTC | 10m |
| 2026-06-05 | FD604 | JAD → BUY | Jun 5, 11:40 UTC | Jun 5, 12:15 UTC | 35m |
| 2026-06-05 | FD604 | - | Jun 5, 07:15 UTC | Jun 5, 07:55 UTC | 40m |
| 2026-06-05 | FD604 | - | Jun 5, 05:20 UTC | Jun 5, 06:05 UTC | 45m |
| 2026-06-05 | FD604 | - | Jun 5, 03:55 UTC | Jun 5, 04:25 UTC | 30m |
| 2026-06-05 | FD604 | - | Jun 5, 02:05 UTC | Jun 5, 02:35 UTC | 30m |
| 2026-06-04 | FD604 | - | Jun 4, 13:30 UTC | Jun 4, 14:10 UTC | 40m |
| 2026-06-04 | FD604 | - | Jun 4, 06:40 UTC | Jun 4, 07:35 UTC | 55m |
| 2026-06-04 | FD604 | BQB → JAD | Jun 4, 01:35 UTC | Jun 4, 02:15 UTC | 40m |
| 2026-06-04 | FD604 | - | Jun 4, 01:15 UTC | Jun 4, 01:30 UTC | 15m |
| 2026-06-04 | FD604 | JAD → BQB | Jun 4, 00:10 UTC | Jun 4, 01:00 UTC | 50m |
| 2026-06-03 | FD604 | - | Jun 3, 09:20 UTC | Jun 3, 10:05 UTC | 45m |
| 2026-06-03 | FD604 | - | Jun 3, 06:15 UTC | Jun 3, 07:00 UTC | 45m |
| 2026-06-03 | FD604 | - | Jun 3, 03:50 UTC | Jun 3, 04:40 UTC | 50m |
| 2026-06-02 | FD604 | - | Jun 2, 23:40 UTC | Jun 3, 00:35 UTC | 55m |
| 2026-06-02 | FD604 | - | Jun 2, 20:15 UTC | Jun 2, 20:50 UTC | 35m |
| 2026-06-02 | FD604 | - | Jun 2, 18:55 UTC | Jun 2, 19:15 UTC | 20m |
| 2026-06-02 | FD604 | - | Jun 2, 17:20 UTC | Jun 2, 17:50 UTC | 30m |
| 2026-06-02 | FD604 | - | Jun 2, 16:25 UTC | Jun 2, 16:40 UTC | 15m |
| 2026-06-02 | FD604 | JAD → KGI | Jun 2, 12:50 UTC | Jun 2, 13:55 UTC | 1h 5m |
| 2026-06-02 | FD604 | - | Jun 2, 09:50 UTC | Jun 2, 10:30 UTC | 40m |
| 2026-06-02 | FD604 | - | Jun 2, 07:20 UTC | Jun 2, 08:05 UTC | 45m |
| 2026-06-02 | FD604 | - | Jun 2, 04:10 UTC | Jun 2, 04:35 UTC | 25m |
| 2026-06-02 | FD604 | - | Jun 2, 02:45 UTC | Jun 2, 03:00 UTC | 15m |
| 2026-06-01 | FD604 | - | Jun 1, 14:55 UTC | Jun 1, 15:20 UTC | 25m |
| 2026-06-01 | FD604 | - | Jun 1, 13:00 UTC | Jun 1, 13:55 UTC | 55m |
| 2026-06-01 | FD604 | - | Jun 1, 11:10 UTC | Jun 1, 11:55 UTC | 45m |
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-OWG page for operator, model, and routing details .