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
- 222
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 24d 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 | - | 13 | 2026-06-17 |
| ADY127 | Aerodyne | 13 | 2026-06-16 |
| ADY131 | Aerodyne | 10 | 2026-06-13 |
| ADY061 | Aerodyne | 10 | 2026-06-07 |
| ADY383 | Aerodyne | 9 | 2026-06-08 |
| ADY133 | Aerodyne | 8 | 2026-06-13 |
| ADY062 | Aerodyne | 8 | 2026-06-07 |
| ADY132 | Aerodyne | 7 | 2026-06-05 |
| ADY064 | - | 7 | 2026-06-18 |
| ADY181 | Aerodyne | 6 | 2026-05-29 |
| ADY142 | Aerodyne | 6 | 2026-06-06 |
| ADY134 | - | 6 | 2026-06-14 |
| ADY063 | - | 6 | 2026-06-17 |
| ADY384 | Aerodyne | 5 | 2026-06-09 |
| ADY1611 | - | 5 | 2026-05-23 |
| ADY715 | Aerodyne | 4 | 2026-06-02 |
| ADY167 | Aerodyne | 4 | 2026-06-04 |
| ADY1610 | - | 4 | 2026-05-23 |
| ADY141 | Aerodyne | 4 | 2026-05-15 |
| ADY032 | Aerodyne | 4 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | ADY994 | - | Jun 19, 23:19 UTC | Jun 19, 23:54 UTC | 35m |
| 2026-06-19 | ADY139 | - | Jun 19, 17:55 UTC | Jun 19, 20:19 UTC | 2h 25m |
| 2026-06-19 | ADY138 | AUH → ADJ | Jun 19, 16:25 UTC | Jun 19, 16:44 UTC | 20m |
| 2026-06-19 | ADY138 | AUH → ADJ | Jun 19, 14:19 UTC | Jun 19, 14:54 UTC | 35m |
| 2026-06-18 | ADY414 | - | Jun 18, 22:30 UTC | Jun 19, 04:50 UTC | 6h 19m |
| 2026-06-18 | ADY064 | - | Jun 18, 19:40 UTC | Jun 18, 19:50 UTC | 10m |
| 2026-06-18 | ADY064 | - | Jun 18, 15:25 UTC | Jun 18, 18:25 UTC | 3h 0m |
| 2026-06-17 | ADY063 | - | Jun 17, 21:25 UTC | Jun 18, 14:20 UTC | 16h 55m |
| 2026-06-17 | ADY033 | AMM → AUH | Jun 17, 10:15 UTC | Jun 17, 12:40 UTC | 2h 25m |
| 2026-06-17 | ADY032 | AUH → AMM | Jun 17, 09:10 UTC | Jun 17, 09:20 UTC | 10m |
| 2026-06-17 | ADY128 | - | Jun 17, 00:25 UTC | Jun 17, 07:35 UTC | 7h 10m |
| 2026-06-16 | ADY127 | AUH → COK | Jun 16, 21:35 UTC | Jun 16, 23:15 UTC | 1h 40m |
| 2026-06-16 | ADY127 | AUH → COK | Jun 16, 03:10 UTC | Jun 16, 23:15 UTC | 20h 6m |
| 2026-06-16 | ADY311 | - | Jun 16, 00:55 UTC | Jun 16, 01:19 UTC | 25m |
| 2026-06-15 | ADY182 | CCJ → AUH | Jun 15, 11:24 UTC | Jun 16, 00:24 UTC | 13h 0m |
| 2026-06-15 | ADY128 | - | Jun 15, 00:05 UTC | Jun 15, 07:45 UTC | 7h 40m |
| 2026-06-14 | ADY441 | AUH → EVN | Jun 14, 06:20 UTC | Jun 14, 22:55 UTC | 16h 35m |
| 2026-06-14 | ADY441 | AUH → EVN | Jun 14, 01:55 UTC | Jun 14, 22:55 UTC | 21h 0m |
| 2026-06-14 | ADY134 | - | Jun 14, 00:25 UTC | Jun 14, 22:55 UTC | 22h 31m |
| 2026-06-13 | ADY133 | AUH → TRV | Jun 13, 08:25 UTC | Jun 13, 23:20 UTC | 14h 55m |
| 2026-06-13 | ADY131 | AUH → TRV | Jun 13, 05:35 UTC | Jun 13, 07:25 UTC | 1h 50m |
| 2026-06-12 | ADY131 | AUH → TRV | Jun 12, 10:55 UTC | Jun 13, 07:25 UTC | 20h 29m |
| 2026-06-12 | ADY128 | COK → AUH | Jun 12, 00:20 UTC | Jun 12, 07:30 UTC | 7h 10m |
| 2026-06-11 | ADY127 | AUH → COK | Jun 11, 21:45 UTC | Jun 11, 23:20 UTC | 1h 35m |
| 2026-06-10 | ADY442 | EVN → AUH | Jun 10, 23:15 UTC | Jun 11, 16:05 UTC | 16h 50m |
| 2026-06-10 | ADY709 | CMB → AUH | Jun 10, 17:05 UTC | Jun 11, 16:05 UTC | 23h 0m |
| 2026-06-10 | ADY708 | AUH → CMB | Jun 10, 13:10 UTC | Jun 11, 10:05 UTC | 20h 55m |
| 2026-06-10 | ADY708 | AUH → CMB | Jun 10, 07:05 UTC | Jun 11, 05:05 UTC | 22h 0m |
| 2026-06-10 | ADY044 | KTM → AUH | Jun 10, 05:15 UTC | Jun 11, 05:00 UTC | 23h 45m |
| 2026-06-10 | ADY044 | KTM → AUH | Jun 10, 04:45 UTC | Jun 10, 23:20 UTC | 18h 35m |
| 2026-06-10 | ADY043 | AUH → KTM | Jun 10, 01:20 UTC | Jun 10, 03:40 UTC | 2h 20m |
| 2026-06-09 | ADY405 | HBE → AUH | Jun 9, 12:35 UTC | Jun 9, 15:40 UTC | 3h 5m |
| 2026-06-09 | ADY384 | SPX → AUH | Jun 9, 00:15 UTC | Jun 9, 11:15 UTC | 11h 0m |
| 2026-06-08 | ADY383 | AUH → SPX | Jun 8, 20:30 UTC | Jun 8, 23:10 UTC | 2h 40m |
| 2026-06-08 | ADY383 | AUH → SPX | Jun 8, 02:05 UTC | Jun 8, 23:10 UTC | 21h 5m |
| 2026-06-08 | ADY383 | AUH → SPX | Jun 8, 00:10 UTC | Jun 8, 22:55 UTC | 22h 45m |
| 2026-06-07 | ADY062 | CGP → AUH | Jun 7, 15:25 UTC | Jun 8, 02:15 UTC | 10h 50m |
| 2026-06-07 | ADY061 | AUH → CGP | Jun 7, 13:30 UTC | Jun 7, 14:05 UTC | 35m |
| 2026-06-06 | ADY402 | HBE → AUH | Jun 6, 23:09 UTC | Jun 7, 02:14 UTC | 3h 5m |
| 2026-06-06 | ADY401 | AUH → ALY | Jun 6, 18:50 UTC | Jun 6, 22:00 UTC | 3h 10m |
| 2026-06-06 | ADY451 | BEY → AUH | Jun 6, 09:39 UTC | Jun 6, 12:24 UTC | 2h 45m |
| 2026-06-06 | ADY142 | MAA → AUH | Jun 6, 00:05 UTC | Jun 6, 01:40 UTC | 1h 35m |
| 2026-06-05 | ADY132 | TRV → AUH | Jun 5, 08:05 UTC | Jun 5, 22:45 UTC | 14h 40m |
| 2026-06-04 | ADY131 | AUH → TRV | Jun 4, 15:25 UTC | Jun 5, 07:10 UTC | 15h 45m |
| 2026-06-04 | ADY131 | AUH → TRV | Jun 4, 09:05 UTC | Jun 5, 07:10 UTC | 22h 5m |
| 2026-06-04 | ADY167 | CCU → AUH | Jun 4, 08:30 UTC | Jun 5, 07:00 UTC | 22h 30m |
| 2026-06-03 | ADY064 | DAC → AUH | Jun 3, 15:50 UTC | Jun 4, 07:25 UTC | 15h 35m |
| 2026-06-02 | ADY063 | AUH → DAC | Jun 2, 23:55 UTC | Jun 3, 14:20 UTC | 14h 25m |
| 2026-06-02 | ADY133 | AUH → TRV | Jun 2, 21:00 UTC | Jun 2, 22:55 UTC | 1h 55m |
| 2026-06-02 | ADY715 | TBS → AUH | Jun 2, 11:45 UTC | Jun 2, 15:20 UTC | 3h 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 A6-AUC page for operator, model, and routing details .