sensors Mode-S transponder
7C4860
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-OKY · PIPER PA-28-140/150/160/180 · operated by MELBOURNE AVIATION GROUP PROPRIETARY LIMITED
- Hex
- 7C4860
- Octal
- 37044140
- Decimal
- 8,144,992
- Country
- AU
- Tail
- VH-OKY
- Type
- P28A
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- AU
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 7C4860 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 |
|---|---|---|---|
| OKY | - | 48 | 2026-07-19 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | OKY | MBW → MBW | Jul 19, 23:20 UTC | Jul 19, 23:55 UTC | 35m |
| 2026-07-19 | OKY | - | Jul 19, 07:05 UTC | Jul 19, 07:35 UTC | 30m |
| 2026-07-19 | OKY | - | Jul 19, 02:40 UTC | Jul 19, 03:20 UTC | 40m |
| 2026-07-16 | OKY | - | Jul 16, 04:30 UTC | Jul 16, 05:30 UTC | 1h 0m |
| 2026-07-16 | OKY | - | Jul 16, 00:45 UTC | Jul 16, 01:10 UTC | 25m |
| 2026-07-12 | OKY | MBW → MBW | Jul 12, 03:15 UTC | Jul 12, 04:05 UTC | 50m |
| 2026-07-11 | OKY | - | Jul 11, 06:45 UTC | Jul 11, 07:10 UTC | 25m |
| 2026-07-11 | OKY | - | Jul 11, 05:01 UTC | Jul 11, 05:31 UTC | 30m |
| 2026-07-11 | OKY | MBW → MBW | Jul 11, 02:55 UTC | Jul 11, 03:45 UTC | 50m |
| 2026-07-10 | OKY | MBW → MBW | Jul 10, 00:15 UTC | Jul 10, 00:50 UTC | 35m |
| 2026-07-06 | OKY | MBW → MBW | Jul 6, 04:05 UTC | Jul 6, 04:55 UTC | 50m |
| 2026-07-05 | OKY | MBW → MBW | Jul 5, 03:40 UTC | Jul 5, 05:10 UTC | 1h 30m |
| 2026-06-29 | OKY | MBW → MBW | Jun 29, 08:04 UTC | Jun 29, 08:29 UTC | 25m |
| 2026-06-28 | OKY | - | Jun 28, 05:55 UTC | Jun 28, 06:10 UTC | 15m |
| 2026-06-28 | OKY | - | Jun 28, 03:14 UTC | Jun 28, 03:35 UTC | 20m |
| 2026-06-28 | OKY | MBW → MBW | Jun 28, 01:34 UTC | Jun 28, 02:44 UTC | 1h 10m |
| 2026-06-27 | OKY | MBW → MBW | Jun 27, 05:04 UTC | Jun 27, 06:44 UTC | 1h 40m |
| 2026-06-26 | OKY | MBW → MBW | Jun 26, 06:39 UTC | Jun 26, 07:05 UTC | 25m |
| 2026-06-22 | OKY | - | Jun 22, 05:04 UTC | Jun 22, 05:29 UTC | 25m |
| 2026-06-22 | OKY | - | Jun 22, 03:54 UTC | Jun 22, 04:24 UTC | 30m |
| 2026-06-21 | OKY | MBW → MBW | Jun 21, 07:14 UTC | Jun 21, 07:34 UTC | 20m |
| 2026-06-16 | OKY | MBW → MBW | Jun 16, 06:25 UTC | Jun 16, 06:59 UTC | 35m |
| 2026-06-08 | OKY | MBW → MBW | Jun 8, 02:50 UTC | Jun 8, 03:40 UTC | 50m |
| 2026-06-07 | OKY | MBW → MBW | Jun 7, 04:40 UTC | Jun 7, 05:35 UTC | 55m |
| 2026-06-07 | OKY | MBW → MBW | Jun 7, 01:09 UTC | Jun 7, 01:35 UTC | 25m |
| 2026-06-06 | OKY | MBW → MBW | Jun 6, 04:10 UTC | Jun 6, 05:00 UTC | 50m |
| 2026-05-28 | OKY | MBW → MBW | May 28, 04:20 UTC | May 28, 05:45 UTC | 1h 25m |
| 2026-05-24 | OKY | - | May 24, 06:15 UTC | May 24, 06:40 UTC | 25m |
| 2026-05-23 | OKY | - | May 23, 04:15 UTC | May 23, 05:10 UTC | 55m |
| 2026-05-22 | OKY | MBW → MBW | May 22, 02:25 UTC | May 22, 02:45 UTC | 20m |
| 2026-05-15 | OKY | MBW → MBW | May 15, 03:15 UTC | May 15, 04:00 UTC | 45m |
| 2026-05-14 | OKY | - | May 14, 05:55 UTC | May 14, 06:30 UTC | 35m |
| 2026-05-14 | OKY | - | May 14, 00:05 UTC | May 14, 00:45 UTC | 40m |
| 2026-05-03 | OKY | - | May 3, 01:05 UTC | May 3, 02:45 UTC | 1h 40m |
| 2026-05-01 | OKY | - | May 1, 05:05 UTC | May 1, 06:55 UTC | 1h 50m |
| 2026-04-30 | OKY | - | Apr 30, 06:20 UTC | Apr 30, 07:00 UTC | 40m |
| 2026-04-29 | OKY | - | Apr 29, 23:45 UTC | Apr 30, 00:50 UTC | 1h 5m |
| 2026-04-29 | OKY | MEB → MBW | Apr 29, 10:05 UTC | Apr 29, 10:30 UTC | 25m |
| 2026-04-29 | OKY | MBW → MEB | Apr 29, 07:29 UTC | Apr 29, 07:50 UTC | 20m |
| 2026-04-28 | OKY | - | Apr 28, 09:10 UTC | Apr 28, 09:50 UTC | 40m |
| 2026-04-28 | OKY | - | Apr 28, 04:45 UTC | Apr 28, 05:25 UTC | 40m |
| 2026-04-28 | OKY | MBW → MEB | Apr 28, 04:00 UTC | Apr 28, 04:15 UTC | 15m |
| 2026-04-26 | OKY | - | Apr 26, 04:10 UTC | Apr 26, 04:50 UTC | 40m |
| 2026-04-24 | OKY | - | Apr 24, 04:40 UTC | Apr 24, 05:20 UTC | 40m |
| 2026-04-21 | OKY | MBW → MBW | Apr 21, 03:30 UTC | Apr 21, 04:30 UTC | 1h 0m |
| 2026-04-20 | OKY | MBW → MBW | Apr 20, 23:40 UTC | Apr 21, 01:30 UTC | 1h 50m |
| 2026-04-18 | OKY | - | Apr 18, 03:45 UTC | Apr 18, 04:20 UTC | 35m |
| 2026-04-15 | OKY | - | Apr 15, 00:00 UTC | Apr 15, 00:35 UTC | 35m |
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-OKY page for operator, model, and routing details .