sensors Mode-S transponder
7C1CE4
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-FZQ · PILATUS PC-24 · operated by ROYAL FLYING DOCTOR SERVICE OF AUSTRALIA CENTRAL OPERATIONS
- Hex
- 7C1CE4
- Octal
- 37016344
- Decimal
- 8,133,860
- Country
- AU
- Tail
- VH-FZQ
- Type
- PC24
- Flights observed
- 47
- Distinct callsigns
- 8
- Country
- AU
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 7C1CE4 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 8 distinct
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | FD803 | - | Jul 23, 04:15 UTC | Jul 23, 04:45 UTC | 30m |
| 2026-07-23 | FD803 | - | Jul 23, 00:40 UTC | Jul 23, 01:10 UTC | 30m |
| 2026-07-22 | FD803 | ADL → ADL | Jul 22, 03:50 UTC | Jul 23, 01:10 UTC | 21h 20m |
| 2026-07-22 | FD803 | - | Jul 22, 01:35 UTC | Jul 22, 02:10 UTC | 35m |
| 2026-07-21 | FD803 | ADL → ADL | Jul 21, 04:20 UTC | Jul 22, 02:10 UTC | 21h 50m |
| 2026-07-21 | FD803 | - | Jul 21, 00:00 UTC | Jul 21, 00:30 UTC | 30m |
| 2026-07-18 | FD804 | - | Jul 18, 04:00 UTC | Jul 18, 04:30 UTC | 30m |
| 2026-07-18 | FD804 | - | Jul 18, 01:15 UTC | Jul 18, 01:54 UTC | 40m |
| 2026-07-17 | FD804 | ADL → ADL | Jul 17, 06:25 UTC | Jul 18, 01:54 UTC | 19h 30m |
| 2026-07-17 | FD805 | - | Jul 17, 02:10 UTC | Jul 17, 02:45 UTC | 35m |
| 2026-07-15 | FD805 | - | Jul 15, 03:35 UTC | Jul 15, 04:05 UTC | 30m |
| 2026-07-14 | FD803 | MEB → ADL | Jul 14, 18:20 UTC | Jul 15, 02:25 UTC | 8h 4m |
| 2026-07-14 | FD803 | ADL → MEB | Jul 14, 07:50 UTC | Jul 14, 17:20 UTC | 9h 30m |
| 2026-07-14 | FD807 | - | Jul 14, 04:50 UTC | Jul 14, 05:25 UTC | 35m |
| 2026-07-10 | FD805 | - | Jul 10, 05:15 UTC | Jul 10, 05:45 UTC | 30m |
| 2026-07-10 | FD805 | - | Jul 10, 02:20 UTC | Jul 10, 02:50 UTC | 30m |
| 2026-07-09 | FD805 | - | Jul 9, 05:05 UTC | Jul 10, 02:50 UTC | 21h 45m |
| 2026-07-09 | FD803 | - | Jul 9, 03:25 UTC | Jul 9, 03:55 UTC | 30m |
| 2026-07-08 | FD803 | ADL → ADL | Jul 8, 05:25 UTC | Jul 9, 03:55 UTC | 22h 30m |
| 2026-07-08 | FD803 | - | Jul 8, 01:15 UTC | Jul 8, 01:50 UTC | 35m |
| 2026-07-07 | FD807 | ADL → ADL | Jul 7, 05:35 UTC | Jul 8, 01:50 UTC | 20h 15m |
| 2026-07-07 | FD807 | - | Jul 7, 01:55 UTC | Jul 7, 02:25 UTC | 30m |
| 2026-07-05 | FD805 | - | Jul 5, 07:40 UTC | Jul 5, 08:10 UTC | 30m |
| 2026-07-05 | FD805 | - | Jul 5, 05:20 UTC | Jul 5, 05:50 UTC | 30m |
| 2026-07-03 | FD803 | - | Jul 3, 04:10 UTC | Jul 3, 04:45 UTC | 35m |
| 2026-07-02 | FD803 | - | Jul 2, 07:05 UTC | Jul 3, 02:10 UTC | 19h 5m |
| 2026-07-02 | FD807 | ADL → ADL | Jul 2, 06:45 UTC | Jul 3, 02:10 UTC | 19h 25m |
| 2026-07-02 | FD807 | - | Jul 2, 02:45 UTC | Jul 2, 03:15 UTC | 30m |
| 2026-06-30 | FD803 | - | Jun 30, 03:35 UTC | Jun 30, 04:05 UTC | 30m |
| 2026-06-30 | FD803 | - | Jun 30, 01:25 UTC | Jun 30, 02:00 UTC | 36m |
| 2026-06-27 | FD804 | - | Jun 27, 05:29 UTC | Jun 27, 05:59 UTC | 30m |
| 2026-06-26 | FD803 | ADL → ADL | Jun 26, 07:20 UTC | Jun 27, 02:39 UTC | 19h 20m |
| 2026-06-26 | FD803 | - | Jun 26, 01:54 UTC | Jun 26, 02:30 UTC | 35m |
| 2026-06-25 | FD803 | - | Jun 25, 03:04 UTC | Jun 26, 02:30 UTC | 23h 25m |
| 2026-06-25 | FD803 | - | Jun 25, 02:59 UTC | Jun 25, 03:34 UTC | 35m |
| 2026-06-23 | FD501 | MEB → ADL | Jun 23, 05:24 UTC | Jun 23, 06:34 UTC | 1h 10m |
| 2026-06-23 | FD501 | ADL → MEB | Jun 23, 01:35 UTC | Jun 23, 02:40 UTC | 1h 5m |
| 2026-06-22 | FD507 | - | Jun 22, 07:54 UTC | Jun 22, 08:50 UTC | 55m |
| 2026-06-22 | FD507 | - | Jun 22, 06:45 UTC | Jun 22, 07:04 UTC | 20m |
| 2026-06-19 | FD503 | - | Jun 19, 11:20 UTC | Jun 19, 11:49 UTC | 30m |
| 2026-06-19 | FD503 | - | Jun 19, 05:05 UTC | Jun 19, 05:14 UTC | 10m |
| 2026-06-19 | FD503 | - | Jun 19, 01:10 UTC | Jun 19, 01:45 UTC | 35m |
| 2026-06-16 | FD508 | MEB → ADL | Jun 16, 04:00 UTC | Jun 16, 05:20 UTC | 1h 20m |
| 2026-06-16 | FD508 | ADL → MEB | Jun 16, 00:50 UTC | Jun 16, 01:50 UTC | 1h 0m |
| 2026-06-12 | FD508 | - | Jun 12, 11:35 UTC | Jun 12, 11:55 UTC | 20m |
| 2026-06-12 | FD508 | - | Jun 12, 10:15 UTC | Jun 12, 10:35 UTC | 20m |
| 2026-06-12 | FD508 | ADL → ADL | Jun 12, 07:00 UTC | Jun 12, 07:20 UTC | 20m |
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-FZQ page for operator, model, and routing details .