sensors Mode-S transponder
8965AC
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-AUC · AIRBUS A-320
- Hex
- 8965AC
- Octal
- 42262654
- Decimal
- 9,004,460
- Country
- AE
- Tail
- A6-AUC
- Type
- A320
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 8965AC falls within the block assigned to United Arab Emirates (AE) by ICAO Annex 10, Volume III. Every aircraft registered in United Arab Emirates 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 |
|---|---|---|---|
| ADY128 | Aerodyne | 11 | 2026-05-30 |
| ADY127 | Aerodyne | 10 | 2026-05-29 |
| ADY061 | Aerodyne | 9 | 2026-05-22 |
| ADY062 | Aerodyne | 7 | 2026-05-22 |
| ADY181 | Aerodyne | 6 | 2026-05-29 |
| ADY133 | Aerodyne | 6 | 2026-05-25 |
| ADY132 | Aerodyne | 6 | 2026-05-11 |
| ADY131 | Aerodyne | 6 | 2026-05-10 |
| ADY1611 | - | 5 | 2026-05-23 |
| ADY142 | Aerodyne | 5 | 2026-05-16 |
| ADY134 | Aerodyne | 5 | 2026-05-24 |
| ADY1610 | - | 4 | 2026-05-23 |
| ADY141 | Aerodyne | 4 | 2026-05-15 |
| ADY064 | Aerodyne | 4 | 2026-05-27 |
| ADY063 | Aerodyne | 4 | 2026-05-27 |
| ADY384 | Aerodyne | 3 | 2026-05-21 |
| ADY335 | Aerodyne | 3 | 2026-05-18 |
| ADY315 | Aerodyne | 3 | 2026-04-19 |
| ADY249 | Aerodyne | 3 | 2026-05-28 |
| ADY248 | Aerodyne | 3 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | ADY128 | COK → AUH | May 30, 00:00 UTC | May 30, 01:30 UTC | 1h 30m |
| 2026-05-29 | ADY127 | AUH → COK | May 29, 10:55 UTC | May 29, 22:50 UTC | 11h 55m |
| 2026-05-29 | ADY181 | AUH → CCJ | May 29, 07:05 UTC | May 29, 07:25 UTC | 20m |
| 2026-05-28 | ADY249 | TRV → AUH | May 28, 14:25 UTC | May 29, 03:20 UTC | 12h 55m |
| 2026-05-28 | ADY248 | AUH → TRV | May 28, 01:15 UTC | May 28, 13:25 UTC | 12h 10m |
| 2026-05-27 | ADY064 | DAC → AUH | May 27, 15:10 UTC | May 27, 23:55 UTC | 8h 45m |
| 2026-05-27 | ADY063 | AUH → DAC | May 27, 00:25 UTC | May 27, 14:05 UTC | 13h 41m |
| 2026-05-26 | ADY715 | TBS → AUH | May 26, 11:54 UTC | May 26, 22:59 UTC | 11h 5m |
| 2026-05-26 | ADY714 | AUH → TBS | May 26, 00:00 UTC | May 26, 10:14 UTC | 10h 15m |
| 2026-05-25 | ADY133 | AUH → TRV | May 25, 20:55 UTC | May 25, 22:55 UTC | 2h 0m |
| 2026-05-25 | ADY181 | AUH → CCJ | May 25, 07:15 UTC | May 25, 07:40 UTC | 25m |
| 2026-05-24 | ADY134 | TRV → AUH | May 24, 23:40 UTC | May 24, 23:46 UTC | 6m |
| 2026-05-24 | ADY715 | TBS → AUH | May 24, 11:10 UTC | May 24, 21:05 UTC | 9h 55m |
| 2026-05-24 | ADY714 | AUH → TBS | May 24, 09:15 UTC | May 24, 09:50 UTC | 35m |
| 2026-05-23 | ADY402 | HBE → AUH | May 23, 23:10 UTC | May 24, 02:00 UTC | 2h 50m |
| 2026-05-23 | ADY401 | AUH → ALY | May 23, 18:55 UTC | May 23, 22:20 UTC | 3h 25m |
| 2026-05-23 | ADY1611 | - | May 23, 11:55 UTC | May 23, 14:40 UTC | 2h 45m |
| 2026-05-23 | ADY1610 | - | May 23, 09:45 UTC | May 23, 11:05 UTC | 1h 20m |
| 2026-05-23 | ADY312 | SKT → AUH | May 23, 00:10 UTC | May 23, 04:55 UTC | 4h 44m |
| 2026-05-22 | ADY311 | AUH → SKT | May 22, 22:05 UTC | May 22, 22:25 UTC | 20m |
| 2026-05-22 | ADY062 | CGP → AUH | May 22, 15:15 UTC | May 22, 18:35 UTC | 3h 20m |
| 2026-05-22 | ADY061 | AUH → CGP | May 22, 00:10 UTC | May 22, 14:05 UTC | 13h 55m |
| 2026-05-21 | ADY061 | AUH → CGP | May 21, 17:20 UTC | May 22, 14:05 UTC | 20h 45m |
| 2026-05-21 | ADY061 | AUH → CGP | May 21, 15:10 UTC | May 22, 14:05 UTC | 22h 55m |
| 2026-05-21 | ADY063 | AUH → DAC | May 21, 10:55 UTC | May 21, 13:55 UTC | 3h 0m |
| 2026-05-21 | ADY384 | SPX → AUH | May 21, 00:35 UTC | May 21, 02:55 UTC | 2h 20m |
| 2026-05-20 | ADY184 | COK → AUH | May 20, 09:40 UTC | May 20, 23:00 UTC | 13h 20m |
| 2026-05-19 | ADY183 | AUH → COK | May 19, 23:45 UTC | May 20, 08:40 UTC | 8h 56m |
| 2026-05-19 | ADY127 | AUH → COK | May 19, 21:10 UTC | May 19, 22:45 UTC | 1h 35m |
| 2026-05-19 | ADY018 | BAH → AUH | May 19, 15:25 UTC | May 19, 15:55 UTC | 30m |
| 2026-05-19 | ADY017 | WAG → MRO | May 19, 14:00 UTC | May 19, 14:10 UTC | 10m |
| 2026-05-18 | ADY062 | CGP → AUH | May 18, 17:35 UTC | May 18, 20:50 UTC | 3h 14m |
| 2026-05-18 | ADY061 | AUH → CGP | May 18, 11:00 UTC | May 18, 14:00 UTC | 3h 0m |
| 2026-05-18 | ADY335 | AUH → MUX | May 18, 04:20 UTC | May 18, 04:25 UTC | 5m |
| 2026-05-17 | ADY139 | - | May 17, 19:50 UTC | May 17, 20:35 UTC | 45m |
| 2026-05-16 | ADY142 | MAA → AUH | May 16, 23:40 UTC | May 17, 01:10 UTC | 1h 30m |
| 2026-05-16 | ADY1611 | - | May 16, 12:16 UTC | May 16, 22:05 UTC | 9h 50m |
| 2026-05-15 | ADY142 | MAA → AUH | May 15, 23:50 UTC | May 16, 10:16 UTC | 10h 26m |
| 2026-05-15 | ADY141 | AUH → MAA | May 15, 20:50 UTC | May 15, 22:20 UTC | 1h 30m |
| 2026-05-15 | ADY181 | AUH → CCJ | May 15, 05:35 UTC | May 15, 05:45 UTC | 10m |
| 2026-05-14 | ADY1611 | - | May 14, 11:50 UTC | May 14, 22:50 UTC | 11h 0m |
| 2026-05-14 | ADY1610 | - | May 14, 00:00 UTC | May 14, 10:50 UTC | 10h 50m |
| 2026-05-13 | ADY133 | AUH → TRV | May 13, 22:20 UTC | May 13, 23:05 UTC | 45m |
| 2026-05-13 | ADY249 | TRV → AUH | May 13, 14:00 UTC | May 13, 14:35 UTC | 35m |
| 2026-05-13 | ADY248 | AUH → TRV | May 13, 12:20 UTC | May 13, 13:05 UTC | 45m |
| 2026-05-13 | ADY336 | MUX → AUH | May 13, 04:55 UTC | May 13, 05:05 UTC | 10m |
| 2026-05-13 | ADY335 | AUH → MUX | May 13, 03:50 UTC | May 13, 04:00 UTC | 10m |
| 2026-05-12 | ADY126 | COK → AUH | May 12, 16:30 UTC | May 12, 16:55 UTC | 25m |
| 2026-05-12 | ADY125 | AUH → COK | May 12, 14:55 UTC | May 12, 15:25 UTC | 30m |
| 2026-05-11 | ADY132 | TRV → AUH | May 11, 08:10 UTC | May 11, 22:35 UTC | 14h 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 A6-AUC page for operator, model, and routing details .