sensors Mode-S transponder
8966C7
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BNK · BOEING 787-9 Dreamliner
- Hex
- 8966C7
- Octal
- 42263307
- Decimal
- 9,004,743
- Country
- AE
- Tail
- A6-BNK
- Type
- B789
- Flights observed
- 190
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 59m ago
Last known position
Country allocation
The ICAO 24-bit address 8966C7 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 |
|---|---|---|---|
| ETD13 | Etihad Airways | 22 | 2026-06-10 |
| ETD47B | - | 18 | 2026-07-02 |
| ETD9SM | Etihad Airways | 11 | 2026-06-11 |
| ETD91N | - | 11 | 2026-07-03 |
| ETD6HZ | Etihad Airways | 9 | 2026-04-18 |
| ETD67B | - | 9 | 2026-06-28 |
| ETD2NL | - | 9 | 2026-07-04 |
| ETD6PX | Etihad Airways | 8 | 2026-05-28 |
| ETD128 | - | 8 | 2026-06-28 |
| ETD16 | - | 7 | 2026-07-02 |
| ETD53M | Etihad Airways | 6 | 2026-04-17 |
| ETD3MB | Etihad Airways | 6 | 2026-05-28 |
| ETD125 | Etihad Airways | 5 | 2026-05-04 |
| ETD99P | Etihad Airways | 4 | 2026-05-05 |
| ETD871 | Etihad Airways | 4 | 2026-06-12 |
| ETD870 | Etihad Airways | 4 | 2026-06-11 |
| ETD801 | Etihad Airways | 4 | 2026-04-30 |
| ETD800 | Etihad Airways | 4 | 2026-04-29 |
| ETD93C | - | 3 | 2026-07-14 |
| ETD7EE | - | 3 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ETD93C | - | Jul 14, 00:30 UTC | Jul 14, 07:45 UTC | 7h 15m |
| 2026-07-13 | ETD7EE | - | Jul 13, 01:40 UTC | Jul 13, 15:10 UTC | 13h 30m |
| 2026-07-12 | ETD4RL | - | Jul 12, 06:35 UTC | Jul 12, 20:05 UTC | 13h 30m |
| 2026-07-12 | ETD11Y | - | Jul 12, 00:30 UTC | Jul 12, 02:35 UTC | 2h 5m |
| 2026-07-11 | ETD11Y | - | Jul 11, 21:25 UTC | Jul 12, 00:25 UTC | 3h 0m |
| 2026-07-11 | ETD6XY | AYM → FCO | Jul 11, 10:30 UTC | Jul 11, 15:45 UTC | 5h 15m |
| 2026-07-08 | ETD76T | - | Jul 8, 02:20 UTC | Jul 8, 15:15 UTC | 12h 55m |
| 2026-07-06 | ETD93C | - | Jul 6, 23:35 UTC | Jul 7, 13:25 UTC | 13h 50m |
| 2026-07-06 | ETD4EH | - | Jul 6, 20:25 UTC | Jul 6, 20:50 UTC | 25m |
| 2026-07-06 | ETD8PF | - | Jul 6, 17:20 UTC | Jul 6, 17:35 UTC | 15m |
| 2026-07-06 | ETD7EE | - | Jul 6, 13:55 UTC | Jul 6, 14:50 UTC | 55m |
| 2026-07-06 | ETD7EE | - | Jul 6, 02:05 UTC | Jul 6, 12:55 UTC | 10h 50m |
| 2026-07-05 | ETD4RL | - | Jul 5, 06:45 UTC | Jul 5, 20:50 UTC | 14h 5m |
| 2026-07-04 | ETD2NL | - | Jul 4, 08:05 UTC | Jul 4, 21:10 UTC | 13h 5m |
| 2026-07-03 | ETD91N | - | Jul 3, 17:40 UTC | Jul 4, 05:55 UTC | 12h 15m |
| 2026-07-02 | ETD16 | - | Jul 2, 19:25 UTC | Jul 3, 08:00 UTC | 12h 35m |
| 2026-07-02 | ETD47B | - | Jul 2, 02:25 UTC | Jul 2, 14:10 UTC | 11h 45m |
| 2026-07-01 | ETD47B | - | Jul 1, 23:55 UTC | Jul 2, 02:20 UTC | 2h 25m |
| 2026-07-01 | ETD2NL | MEL → AUH | Jul 1, 07:55 UTC | Jul 1, 21:25 UTC | 13h 30m |
| 2026-06-30 | ETD91N | - | Jun 30, 17:50 UTC | Jul 1, 06:10 UTC | 12h 20m |
| 2026-06-30 | ETD012 | - | Jun 30, 02:25 UTC | Jun 30, 15:50 UTC | 13h 25m |
| 2026-06-29 | ETD011 | - | Jun 29, 06:44 UTC | Jun 29, 20:24 UTC | 13h 40m |
| 2026-06-28 | ETD128 | MUC → AUH | Jun 28, 20:50 UTC | Jun 29, 02:09 UTC | 5h 20m |
| 2026-06-28 | ETD67B | AYM → MUC | Jun 28, 10:39 UTC | Jun 28, 16:29 UTC | 5h 50m |
| 2026-06-27 | ETD76T | - | Jun 27, 19:39 UTC | Jun 28, 08:34 UTC | 12h 55m |
| 2026-06-26 | ETD93C | - | Jun 26, 23:19 UTC | Jun 27, 06:30 UTC | 7h 10m |
| 2026-06-25 | ETD012A | - | Jun 25, 22:14 UTC | Jun 26, 11:20 UTC | 13h 5m |
| 2026-06-21 | ETD011 | - | Jun 21, 06:24 UTC | Jun 21, 20:34 UTC | 14h 10m |
| 2026-06-20 | ETD11Y | - | Jun 20, 21:14 UTC | Jun 21, 02:40 UTC | 5h 25m |
| 2026-06-20 | ETD6XY | - | Jun 20, 10:25 UTC | Jun 20, 13:44 UTC | 3h 20m |
| 2026-06-19 | ETD473 | - | Jun 19, 18:05 UTC | Jun 19, 21:39 UTC | 3h 35m |
| 2026-06-19 | ETD473 | - | Jun 19, 17:14 UTC | Jun 19, 17:29 UTC | 15m |
| 2026-06-19 | ETD472 | - | Jun 19, 07:09 UTC | Jun 19, 13:14 UTC | 6h 5m |
| 2026-06-19 | ETD472 | - | Jun 19, 05:24 UTC | Jun 19, 05:40 UTC | 15m |
| 2026-06-18 | ETD358 | - | Jun 18, 12:45 UTC | Jun 18, 18:00 UTC | 5h 15m |
| 2026-06-18 | ETD16 | - | Jun 18, 02:40 UTC | Jun 18, 07:50 UTC | 5h 10m |
| 2026-06-17 | ETD16 | - | Jun 17, 19:15 UTC | Jun 18, 02:35 UTC | 7h 20m |
| 2026-06-17 | ETD47B | - | Jun 17, 00:40 UTC | Jun 17, 14:30 UTC | 13h 50m |
| 2026-06-16 | ETD47B | - | Jun 16, 17:49 UTC | Jun 17, 14:30 UTC | 20h 41m |
| 2026-06-16 | ETD47B | - | Jun 16, 17:24 UTC | Jun 17, 14:30 UTC | 21h 6m |
| 2026-06-16 | ETD47B | - | Jun 16, 10:45 UTC | Jun 17, 08:55 UTC | 22h 11m |
| 2026-06-16 | ETD47B | - | Jun 16, 07:50 UTC | Jun 17, 07:45 UTC | 23h 56m |
| 2026-06-16 | ETD2NL | - | Jun 16, 07:40 UTC | Jun 17, 05:45 UTC | 22h 6m |
| 2026-06-15 | ETD91N | - | Jun 15, 20:00 UTC | Jun 16, 05:40 UTC | 9h 40m |
| 2026-06-14 | ETD16 | - | Jun 14, 19:35 UTC | Jun 15, 08:10 UTC | 12h 34m |
| 2026-06-14 | ETD47B | - | Jun 14, 00:35 UTC | Jun 14, 14:20 UTC | 13h 45m |
| 2026-06-13 | ETD47B | - | Jun 13, 18:00 UTC | Jun 14, 14:20 UTC | 20h 20m |
| 2026-06-13 | ETD47B | - | Jun 13, 17:05 UTC | Jun 14, 14:20 UTC | 21h 15m |
| 2026-06-13 | ETD47B | - | Jun 13, 08:20 UTC | Jun 14, 07:15 UTC | 22h 55m |
| 2026-06-13 | ETD47B | - | Jun 13, 07:00 UTC | Jun 14, 05:45 UTC | 22h 45m |
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-BNK page for operator, model, and routing details .