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