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