sensors Mode-S transponder
7C4CFA
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-PHO · BELL 206 JetRanger · operated by PROFESSIONAL HELICOPTER SERVICES PTY. LTD.
- Hex
- 7C4CFA
- Octal
- 37046372
- Decimal
- 8,146,170
- Country
- AU
- Tail
- VH-PHO
- Type
- B06
- Flights observed
- 44
- Distinct callsigns
- 2
- Country
- AU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7C4CFA 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 2 distinct
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | ENRGY350 | MBW → MBW | Jul 20, 05:40 UTC | Jul 20, 06:15 UTC | 35m |
| 2026-07-17 | ENRGY350 | MBW → MBW | Jul 17, 05:04 UTC | Jul 17, 05:15 UTC | 10m |
| 2026-07-17 | ENRGY350 | MBW → MBW | Jul 17, 01:39 UTC | Jul 17, 01:55 UTC | 15m |
| 2026-07-16 | ENRGY350 | MBW → MBW | Jul 16, 23:20 UTC | Jul 16, 23:44 UTC | 25m |
| 2026-07-10 | ENRGY350 | - | Jul 10, 06:15 UTC | Jul 10, 06:30 UTC | 15m |
| 2026-07-10 | ENRGY350 | - | Jul 10, 02:40 UTC | Jul 10, 05:05 UTC | 2h 25m |
| 2026-07-05 | PHO | - | Jul 5, 22:45 UTC | Jul 5, 23:05 UTC | 20m |
| 2026-07-03 | PHO | - | Jul 3, 02:00 UTC | Jul 3, 02:20 UTC | 20m |
| 2026-07-02 | PHO | - | Jul 2, 22:50 UTC | Jul 3, 01:00 UTC | 2h 10m |
| 2026-07-01 | PHO | - | Jul 1, 01:35 UTC | Jul 1, 03:30 UTC | 1h 55m |
| 2026-07-01 | PHO | - | Jul 1, 00:10 UTC | Jul 1, 00:25 UTC | 15m |
| 2026-06-30 | PHO | - | Jun 30, 22:50 UTC | Jun 30, 23:05 UTC | 15m |
| 2026-06-29 | PHO | - | Jun 29, 05:20 UTC | Jun 29, 05:40 UTC | 20m |
| 2026-06-29 | PHO | - | Jun 29, 04:00 UTC | Jun 29, 04:09 UTC | 10m |
| 2026-06-29 | PHO | - | Jun 29, 02:09 UTC | Jun 29, 02:59 UTC | 50m |
| 2026-06-29 | PHO | - | Jun 29, 00:05 UTC | Jun 29, 00:49 UTC | 45m |
| 2026-06-28 | PHO | - | Jun 28, 23:09 UTC | Jun 28, 23:25 UTC | 15m |
| 2026-06-20 | PHO | - | Jun 20, 06:19 UTC | Jun 20, 06:45 UTC | 25m |
| 2026-06-19 | PHO | - | Jun 19, 00:14 UTC | Jun 19, 00:24 UTC | 10m |
| 2026-06-14 | PHO | - | Jun 14, 05:10 UTC | Jun 14, 05:40 UTC | 30m |
| 2026-06-11 | PHO | MBW → MBW | Jun 11, 23:00 UTC | Jun 11, 23:45 UTC | 45m |
| 2026-06-11 | PHO | MBW → MBW | Jun 11, 04:15 UTC | Jun 11, 05:00 UTC | 45m |
| 2026-06-11 | PHO | MBW → MBW | Jun 11, 01:15 UTC | Jun 11, 01:40 UTC | 25m |
| 2026-06-10 | PHO | MBW → MBW | Jun 10, 05:30 UTC | Jun 10, 05:55 UTC | 25m |
| 2026-05-29 | PHO | - | May 29, 04:45 UTC | May 29, 05:05 UTC | 20m |
| 2026-05-29 | PHO | - | May 29, 03:05 UTC | May 29, 03:20 UTC | 15m |
| 2026-05-29 | PHO | - | May 29, 02:05 UTC | May 29, 02:25 UTC | 20m |
| 2026-05-28 | PHO | - | May 28, 23:30 UTC | May 29, 01:20 UTC | 1h 50m |
| 2026-05-26 | PHO | - | May 26, 06:14 UTC | May 26, 06:49 UTC | 35m |
| 2026-05-26 | PHO | - | May 26, 04:45 UTC | May 26, 04:54 UTC | 10m |
| 2026-05-26 | PHO | - | May 26, 03:50 UTC | May 26, 04:00 UTC | 10m |
| 2026-05-26 | PHO | - | May 26, 02:04 UTC | May 26, 03:05 UTC | 1h 0m |
| 2026-05-26 | PHO | - | May 26, 01:05 UTC | May 26, 01:24 UTC | 20m |
| 2026-05-25 | PHO | - | May 25, 03:20 UTC | May 25, 05:15 UTC | 1h 55m |
| 2026-05-24 | PHO | - | May 24, 23:10 UTC | May 24, 23:30 UTC | 20m |
| 2026-05-15 | PHO | - | May 15, 01:40 UTC | May 15, 02:00 UTC | 20m |
| 2026-05-11 | PHO | - | May 11, 05:45 UTC | May 11, 06:15 UTC | 30m |
| 2026-05-07 | PHO | - | May 7, 04:50 UTC | May 7, 05:00 UTC | 10m |
| 2026-05-03 | PHO | - | May 3, 23:00 UTC | May 3, 23:15 UTC | 15m |
| 2026-04-22 | PHO | - | Apr 22, 03:00 UTC | Apr 22, 03:30 UTC | 30m |
| 2026-04-20 | PHO | - | Apr 20, 00:50 UTC | Apr 20, 01:05 UTC | 15m |
| 2026-04-19 | PHO | - | Apr 19, 23:30 UTC | Apr 20, 00:05 UTC | 35m |
| 2026-04-17 | PHO | MBW → MBW | Apr 17, 03:30 UTC | Apr 17, 04:50 UTC | 1h 21m |
| 2026-04-17 | PHO | - | Apr 17, 00:10 UTC | Apr 17, 00:35 UTC | 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-PHO page for operator, model, and routing details .