sensors Mode-S transponder
8966C9
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ASM · BOMBARDIER CL-600 Challenger
- Hex
- 8966C9
- Octal
- 42263311
- Decimal
- 9,004,745
- Country
- AE
- Tail
- A6-ASM
- Type
- CL60
- Flights observed
- 44
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 8966C9 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 |
|---|---|---|---|
| A6ASM | - | 7 | 2026-06-29 |
| VGG257 | - | 2 | 2026-07-03 |
| VGG254 | - | 2 | 2026-06-29 |
| VGG246 | - | 2 | 2026-06-18 |
| VGG194 | - | 2 | 2026-05-02 |
| VGG02 | - | 2 | 2026-06-05 |
| VGG268 | - | 1 | 2026-07-16 |
| VGG266 | - | 1 | 2026-07-15 |
| VGG264 | - | 1 | 2026-07-08 |
| VGG262 | - | 1 | 2026-07-05 |
| VGG256 | - | 1 | 2026-06-30 |
| VGG253 | - | 1 | 2026-06-28 |
| VGG252 | - | 1 | 2026-06-19 |
| VGG244 | - | 1 | 2026-06-17 |
| VGG242 | - | 1 | 2026-06-13 |
| VGG241 | - | 1 | 2026-06-11 |
| VGG239 | - | 1 | 2026-06-11 |
| VGG238 | - | 1 | 2026-06-10 |
| VGG226 | - | 1 | 2026-05-23 |
| VGG221 | - | 1 | 2026-05-21 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | VGG268 | - | Jul 16, 15:55 UTC | Jul 16, 17:49 UTC | 1h 55m |
| 2026-07-15 | VGG266 | - | Jul 15, 05:00 UTC | Jul 15, 05:50 UTC | 50m |
| 2026-07-08 | VGG264 | - | Jul 8, 05:35 UTC | Jul 8, 12:10 UTC | 6h 35m |
| 2026-07-05 | VGG262 | - | Jul 5, 00:35 UTC | Jul 5, 06:40 UTC | 6h 5m |
| 2026-07-03 | VGG257 | - | Jul 3, 10:55 UTC | Jul 3, 11:25 UTC | 30m |
| 2026-06-30 | VGG256 | - | Jun 30, 05:40 UTC | Jun 30, 07:50 UTC | 2h 10m |
| 2026-06-29 | A6ASM | - | Jun 29, 18:14 UTC | Jun 29, 18:30 UTC | 15m |
| 2026-06-29 | VGG254 | - | Jun 29, 16:50 UTC | Jun 29, 17:19 UTC | 30m |
| 2026-06-28 | VGG253 | - | Jun 28, 07:34 UTC | Jun 28, 09:55 UTC | 2h 20m |
| 2026-06-27 | A6ASM | - | Jun 27, 14:39 UTC | Jun 27, 15:05 UTC | 25m |
| 2026-06-27 | VGG257 | - | Jun 27, 02:20 UTC | Jun 27, 12:45 UTC | 10h 25m |
| 2026-06-27 | A6ASM | - | Jun 27, 00:50 UTC | Jun 27, 01:00 UTC | 10m |
| 2026-06-23 | A6ASM | - | Jun 23, 16:20 UTC | Jun 23, 16:44 UTC | 25m |
| 2026-06-22 | VGG254 | - | Jun 22, 01:29 UTC | Jun 22, 12:25 UTC | 10h 55m |
| 2026-06-21 | A6ASM | - | Jun 21, 23:40 UTC | Jun 21, 23:44 UTC | 5m |
| 2026-06-19 | VGG252 | DWC → DWC | Jun 19, 17:09 UTC | Jun 19, 21:49 UTC | 4h 40m |
| 2026-06-18 | VGG246 | - | Jun 18, 21:00 UTC | Jun 18, 22:15 UTC | 1h 15m |
| 2026-06-18 | VGG246 | - | Jun 18, 01:05 UTC | Jun 18, 22:15 UTC | 21h 10m |
| 2026-06-17 | VGG244 | - | Jun 17, 17:50 UTC | Jun 18, 01:25 UTC | 7h 35m |
| 2026-06-13 | VGG242 | - | Jun 13, 14:50 UTC | Jun 13, 19:30 UTC | 4h 40m |
| 2026-06-11 | VGG241 | - | Jun 11, 15:30 UTC | Jun 11, 17:15 UTC | 1h 45m |
| 2026-06-11 | VGG239 | VNO → KUN | Jun 11, 13:50 UTC | Jun 11, 14:10 UTC | 20m |
| 2026-06-10 | VGG238 | - | Jun 10, 12:35 UTC | Jun 10, 19:10 UTC | 6h 35m |
| 2026-06-05 | VGG02 | - | Jun 5, 04:45 UTC | Jun 5, 04:55 UTC | 10m |
| 2026-05-27 | VGG02 | - | May 27, 12:05 UTC | May 27, 15:15 UTC | 3h 10m |
| 2026-05-26 | VGG2 | - | May 26, 10:44 UTC | May 26, 11:34 UTC | 50m |
| 2026-05-23 | VGG226 | - | May 23, 00:50 UTC | May 23, 01:35 UTC | 45m |
| 2026-05-21 | VGG221 | - | May 21, 07:10 UTC | May 21, 09:45 UTC | 2h 35m |
| 2026-05-13 | VGG219 | - | May 13, 12:50 UTC | May 13, 13:35 UTC | 45m |
| 2026-05-13 | VGG218 | - | May 13, 07:10 UTC | May 13, 08:10 UTC | 1h 0m |
| 2026-05-04 | VGG213 | - | May 4, 07:45 UTC | May 4, 14:05 UTC | 6h 20m |
| 2026-05-02 | VGG194 | SHJ → SHJ | May 2, 21:50 UTC | May 2, 22:10 UTC | 20m |
| 2026-05-02 | VGG194 | - | May 2, 19:55 UTC | May 2, 20:15 UTC | 20m |
| 2026-04-30 | VGG193 | - | Apr 30, 09:30 UTC | Apr 30, 10:40 UTC | 1h 10m |
| 2026-04-30 | A6ASM | - | Apr 30, 07:25 UTC | Apr 30, 07:55 UTC | 30m |
| 2026-04-29 | VGG212 | - | Apr 29, 21:00 UTC | Apr 29, 21:25 UTC | 25m |
| 2026-04-29 | VGG211 | - | Apr 29, 11:40 UTC | Apr 29, 19:05 UTC | 7h 25m |
| 2026-04-28 | A6ASM | - | Apr 28, 16:40 UTC | Apr 28, 16:50 UTC | 10m |
| 2026-04-28 | VGG209 | - | Apr 28, 15:05 UTC | Apr 28, 15:25 UTC | 20m |
| 2026-04-27 | VGG208 | - | Apr 27, 14:45 UTC | Apr 27, 15:30 UTC | 45m |
| 2026-04-26 | VGG207 | - | Apr 26, 18:05 UTC | Apr 26, 18:35 UTC | 30m |
| 2026-04-26 | VGG206 | - | Apr 26, 10:20 UTC | Apr 26, 11:15 UTC | 55m |
| 2026-04-22 | VGG202 | - | Apr 22, 12:45 UTC | Apr 22, 13:05 UTC | 20m |
| 2026-04-22 | VGG201 | - | Apr 22, 08:20 UTC | Apr 22, 08:40 UTC | 20m |
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-ASM page for operator, model, and routing details .