sensors Mode-S transponder
8966CD
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-MVA · AIRBUS A-320
- Hex
- 8966CD
- Octal
- 42263315
- Decimal
- 9,004,749
- Country
- AE
- Tail
- A6-MVA
- Type
- A320
- Flights observed
- 91
- Distinct callsigns
- 8
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8966CD 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 8 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | VYU132 | - | May 28, 14:50 UTC | May 28, 15:50 UTC | 1h 0m |
| 2026-05-28 | VYU122 | - | May 28, 05:15 UTC | May 28, 06:15 UTC | 1h 0m |
| 2026-05-27 | VYU132 | - | May 27, 14:00 UTC | May 27, 14:45 UTC | 45m |
| 2026-05-26 | VYU124 | - | May 26, 14:05 UTC | May 26, 15:00 UTC | 55m |
| 2026-05-26 | VYU123 | - | May 26, 11:34 UTC | May 26, 12:24 UTC | 50m |
| 2026-05-25 | VYU132 | - | May 25, 16:30 UTC | May 26, 06:49 UTC | 14h 19m |
| 2026-05-25 | VYU131 | - | May 25, 08:40 UTC | May 25, 15:20 UTC | 6h 40m |
| 2026-05-24 | VYU132 | - | May 24, 14:00 UTC | May 25, 06:45 UTC | 16h 45m |
| 2026-05-24 | VYU122 | - | May 24, 04:40 UTC | May 24, 05:30 UTC | 50m |
| 2026-05-23 | VYU121 | - | May 23, 14:55 UTC | May 24, 03:15 UTC | 12h 20m |
| 2026-05-23 | VYU131 | - | May 23, 12:25 UTC | May 23, 13:25 UTC | 1h 0m |
| 2026-05-23 | VYU122 | - | May 23, 07:35 UTC | May 23, 07:45 UTC | 10m |
| 2026-05-23 | VYU122 | - | May 23, 05:10 UTC | May 23, 06:05 UTC | 55m |
| 2026-05-23 | VYU121 | - | May 23, 02:45 UTC | May 23, 03:45 UTC | 1h 0m |
| 2026-05-23 | VYU121 | - | May 23, 01:25 UTC | May 23, 01:45 UTC | 20m |
| 2026-05-22 | VYU124 | - | May 22, 14:45 UTC | May 22, 15:30 UTC | 45m |
| 2026-05-22 | VYU123 | - | May 22, 12:05 UTC | May 22, 12:50 UTC | 45m |
| 2026-05-22 | VYU123 | RKT → RKT | May 22, 10:45 UTC | May 22, 11:15 UTC | 30m |
| 2026-05-22 | VYU122 | - | May 22, 04:35 UTC | May 22, 04:55 UTC | 20m |
| 2026-05-21 | VYU124 | - | May 21, 15:15 UTC | May 21, 16:15 UTC | 1h 0m |
| 2026-05-21 | VYU123 | - | May 21, 11:50 UTC | May 21, 12:45 UTC | 55m |
| 2026-05-21 | VYU123 | - | May 21, 10:30 UTC | May 21, 10:55 UTC | 25m |
| 2026-05-21 | VYU122 | - | May 21, 04:55 UTC | May 21, 05:55 UTC | 1h 0m |
| 2026-05-20 | VYU124 | - | May 20, 15:40 UTC | May 20, 16:35 UTC | 55m |
| 2026-05-20 | VYU123 | - | May 20, 04:25 UTC | May 20, 14:15 UTC | 9h 51m |
| 2026-05-19 | VYU124 | - | May 19, 15:05 UTC | May 19, 15:55 UTC | 50m |
| 2026-05-19 | VYU123 | - | May 19, 12:35 UTC | May 19, 13:30 UTC | 55m |
| 2026-05-19 | VYU123 | - | May 19, 11:15 UTC | May 19, 11:45 UTC | 30m |
| 2026-05-19 | VYU122 | - | May 19, 04:50 UTC | May 19, 05:45 UTC | 55m |
| 2026-05-18 | VYU124 | - | May 18, 15:50 UTC | May 18, 16:25 UTC | 35m |
| 2026-05-18 | VYU123 | - | May 18, 12:55 UTC | May 18, 13:50 UTC | 55m |
| 2026-05-18 | VYU123 | - | May 18, 11:30 UTC | May 18, 12:00 UTC | 30m |
| 2026-05-17 | VYU124 | - | May 17, 15:35 UTC | May 18, 06:55 UTC | 15h 20m |
| 2026-05-17 | VYU121 | - | May 17, 02:45 UTC | May 17, 16:10 UTC | 13h 25m |
| 2026-05-15 | VYU123 | - | May 15, 05:35 UTC | May 15, 16:40 UTC | 11h 4m |
| 2026-05-14 | VYU123 | - | May 14, 15:20 UTC | May 15, 13:55 UTC | 22h 35m |
| 2026-05-14 | VYU124 | - | May 14, 15:10 UTC | May 15, 13:15 UTC | 22h 5m |
| 2026-05-14 | VYU123 | - | May 14, 12:25 UTC | May 15, 06:05 UTC | 17h 40m |
| 2026-05-14 | VYU123 | - | May 14, 02:35 UTC | May 14, 15:55 UTC | 13h 20m |
| 2026-05-14 | VYU121 | - | May 14, 01:10 UTC | May 14, 01:40 UTC | 30m |
| 2026-05-13 | VYU124 | - | May 13, 17:45 UTC | May 13, 18:00 UTC | 15m |
| 2026-05-13 | VYU124 | - | May 13, 12:55 UTC | May 13, 16:20 UTC | 3h 25m |
| 2026-05-13 | VYU123 | - | May 13, 11:30 UTC | May 13, 11:50 UTC | 20m |
| 2026-05-13 | VYU122 | - | May 13, 08:50 UTC | May 13, 09:00 UTC | 10m |
| 2026-05-12 | VYU123 | - | May 12, 12:25 UTC | May 13, 07:15 UTC | 18h 50m |
| 2026-05-12 | VYU122 | - | May 12, 04:45 UTC | May 12, 16:55 UTC | 12h 10m |
| 2026-05-11 | VYU122 | - | May 11, 16:30 UTC | May 12, 13:05 UTC | 20h 36m |
| 2026-05-11 | VYU123 | - | May 11, 13:40 UTC | May 12, 13:05 UTC | 23h 26m |
| 2026-05-11 | VYU122 | - | May 11, 06:15 UTC | May 12, 05:15 UTC | 23h 0m |
| 2026-05-10 | VYU123 | - | May 10, 15:19 UTC | May 11, 14:25 UTC | 23h 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 A6-MVA page for operator, model, and routing details .