sensors Mode-S transponder
7C1ABD
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-FKF · FOKKER 100 · operated by ALLIANCE AIRLINES PTY LIMITED
- Hex
- 7C1ABD
- Octal
- 37015275
- Decimal
- 8,133,309
- Country
- AU
- Tail
- VH-FKF
- Type
- F100
- Flights observed
- 139
- Distinct callsigns
- 20
- Country
- AU
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 7C1ABD 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTY870 | - | 17 | 2026-07-12 |
| UTY731 | - | 8 | 2026-07-06 |
| UTY737 | - | 6 | 2026-06-17 |
| UTY6527 | - | 6 | 2026-06-29 |
| UTY6301 | - | 6 | 2026-07-02 |
| UTY6300 | - | 6 | 2026-07-02 |
| UTY6526 | - | 5 | 2026-07-09 |
| UTY878 | - | 4 | 2026-07-08 |
| UTY751 | - | 4 | 2026-06-24 |
| UTY4120 | - | 4 | 2026-06-25 |
| UTY956 | - | 3 | 2026-07-07 |
| UTY753 | - | 3 | 2026-06-24 |
| UTY752 | - | 3 | 2026-06-24 |
| UTY750 | Alliance Airlines | 3 | 2026-06-24 |
| UTY738 | Alliance Airlines | 3 | 2026-05-19 |
| UTY732 | - | 3 | 2026-06-18 |
| UTY6521 | - | 3 | 2026-07-08 |
| UTY6501 | - | 3 | 2026-06-29 |
| UTY6500 | - | 3 | 2026-06-28 |
| UTY6303 | - | 3 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UTY802 | PER → PER | Jul 13, 22:25 UTC | Jul 14, 01:45 UTC | 3h 20m |
| 2026-07-12 | UTY870 | PER → PER | Jul 12, 23:00 UTC | Jul 13, 10:00 UTC | 11h 0m |
| 2026-07-09 | UTY870 | PER → PER | Jul 9, 23:00 UTC | Jul 10, 10:00 UTC | 11h 0m |
| 2026-07-09 | UTY6526 | PER → PER | Jul 9, 06:50 UTC | Jul 9, 10:05 UTC | 3h 15m |
| 2026-07-08 | UTY6521 | PER → PER | Jul 8, 22:05 UTC | Jul 9, 01:15 UTC | 3h 10m |
| 2026-07-08 | UTY878 | PER → PER | Jul 8, 06:50 UTC | Jul 8, 11:40 UTC | 4h 50m |
| 2026-07-07 | UTY870 | PER → PER | Jul 7, 22:50 UTC | Jul 8, 03:50 UTC | 5h 0m |
| 2026-07-07 | UTY956 | PER → PER | Jul 7, 06:25 UTC | Jul 7, 09:35 UTC | 3h 10m |
| 2026-07-06 | UTY731 | PER → PER | Jul 6, 21:40 UTC | Jul 7, 02:55 UTC | 5h 15m |
| 2026-07-05 | UTY870 | PER → PER | Jul 5, 22:55 UTC | Jul 6, 10:00 UTC | 11h 5m |
| 2026-07-02 | UTY870 | PER → PER | Jul 2, 22:55 UTC | Jul 3, 10:15 UTC | 11h 20m |
| 2026-07-02 | UTY6301 | KGI → PER | Jul 2, 10:45 UTC | Jul 2, 11:55 UTC | 1h 10m |
| 2026-07-02 | UTY6300 | PER → KGI | Jul 2, 07:35 UTC | Jul 2, 08:30 UTC | 55m |
| 2026-07-01 | UTY731 | PER → PER | Jul 1, 21:35 UTC | Jul 2, 02:30 UTC | 4h 55m |
| 2026-07-01 | UTY6303 | KGI → PER | Jul 1, 11:25 UTC | Jul 1, 12:30 UTC | 1h 5m |
| 2026-07-01 | UTY6310 | PER → KGI | Jul 1, 08:15 UTC | Jul 1, 09:15 UTC | 1h 0m |
| 2026-07-01 | UTY6360 | PER → SLJ | Jul 1, 02:30 UTC | Jul 1, 06:45 UTC | 4h 15m |
| 2026-06-30 | UTY6301 | KGI → PER | Jun 30, 23:30 UTC | Jul 1, 00:35 UTC | 1h 5m |
| 2026-06-30 | UTY6300 | PER → KGI | Jun 30, 21:05 UTC | Jun 30, 22:00 UTC | 55m |
| 2026-06-30 | UTY878 | PER → PER | Jun 30, 06:50 UTC | Jun 30, 11:55 UTC | 5h 5m |
| 2026-06-30 | UTY6362 | PER → PER | Jun 30, 00:20 UTC | Jun 30, 04:55 UTC | 4h 36m |
| 2026-06-29 | UTY6527 | PER → PER | Jun 29, 06:44 UTC | Jun 29, 10:00 UTC | 3h 15m |
| 2026-06-29 | UTY6501 | - | Jun 29, 01:05 UTC | Jun 29, 01:44 UTC | 40m |
| 2026-06-28 | UTY6500 | - | Jun 28, 22:59 UTC | Jun 28, 23:29 UTC | 30m |
| 2026-06-25 | UTY4120 | PER → PER | Jun 25, 06:09 UTC | Jun 25, 09:29 UTC | 3h 20m |
| 2026-06-24 | UTY6501 | PER → PER | Jun 24, 22:55 UTC | Jun 25, 01:44 UTC | 2h 50m |
| 2026-06-24 | UTY753 | KGI → PER | Jun 24, 08:14 UTC | Jun 24, 09:19 UTC | 1h 5m |
| 2026-06-24 | UTY752 | PER → KGI | Jun 24, 06:29 UTC | Jun 24, 07:20 UTC | 50m |
| 2026-06-24 | UTY751 | - | Jun 24, 04:50 UTC | Jun 24, 05:24 UTC | 35m |
| 2026-06-24 | UTY751 | - | Jun 24, 04:10 UTC | Jun 24, 04:15 UTC | 5m |
| 2026-06-24 | UTY750 | PER → KGI | Jun 24, 02:20 UTC | Jun 24, 03:15 UTC | 55m |
| 2026-06-23 | UTY952 | PER → PER | Jun 23, 07:49 UTC | Jun 23, 10:39 UTC | 2h 50m |
| 2026-06-22 | UTY870 | PER → PER | Jun 22, 22:54 UTC | Jun 23, 04:00 UTC | 5h 5m |
| 2026-06-21 | UTY870 | PER → PER | Jun 21, 23:50 UTC | Jun 22, 09:54 UTC | 10h 5m |
| 2026-06-19 | UTY6503 | - | Jun 19, 06:59 UTC | Jun 19, 07:34 UTC | 35m |
| 2026-06-19 | UTY6502 | - | Jun 19, 04:50 UTC | Jun 19, 05:14 UTC | 25m |
| 2026-06-18 | UTY732 | PER → PER | Jun 18, 21:40 UTC | Jun 19, 02:24 UTC | 4h 44m |
| 2026-06-18 | UTY5206 | PER → PER | Jun 18, 07:10 UTC | Jun 18, 11:30 UTC | 4h 20m |
| 2026-06-17 | UTY6500 | PER → PER | Jun 17, 23:00 UTC | Jun 18, 01:45 UTC | 2h 45m |
| 2026-06-17 | UTY737 | PER → PER | Jun 17, 06:45 UTC | Jun 17, 11:30 UTC | 4h 45m |
| 2026-06-16 | UTY731 | PER → PER | Jun 16, 21:40 UTC | Jun 17, 02:40 UTC | 5h 0m |
| 2026-06-16 | UTY737 | PER → PER | Jun 16, 06:59 UTC | Jun 16, 11:35 UTC | 4h 35m |
| 2026-06-15 | UTY731 | PER → PER | Jun 15, 21:40 UTC | Jun 16, 02:45 UTC | 5h 5m |
| 2026-06-14 | UTY870 | PER → PER | Jun 14, 22:55 UTC | Jun 15, 09:49 UTC | 10h 54m |
| 2026-06-12 | UTY5208 | PER → PER | Jun 12, 07:20 UTC | Jun 12, 10:10 UTC | 2h 50m |
| 2026-06-11 | UTY6362 | PER → CKW | Jun 11, 23:15 UTC | Jun 12, 04:25 UTC | 5h 11m |
| 2026-06-10 | UTY5204 | PER → PER | Jun 10, 22:35 UTC | Jun 11, 01:30 UTC | 2h 55m |
| 2026-06-10 | UTY737 | PER → KTA | Jun 10, 06:50 UTC | Jun 10, 11:35 UTC | 4h 45m |
| 2026-06-09 | UTY733 | PER → PER | Jun 9, 23:05 UTC | Jun 10, 03:55 UTC | 4h 50m |
| 2026-06-08 | UTY6303 | KGI → PER | Jun 8, 00:05 UTC | Jun 8, 01:10 UTC | 1h 5m |
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-FKF page for operator, model, and routing details .