sensors Mode-S transponder
8966C4
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BNI · BOEING 787-9 Dreamliner
- Hex
- 8966C4
- Octal
- 42263304
- Decimal
- 9,004,740
- Country
- AE
- Tail
- A6-BNI
- Type
- B789
- Flights observed
- 215
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 20:30 UTC
Current position
Country allocation
The ICAO 24-bit address 8966C4 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 |
|---|---|---|---|
| ETD3MB | Etihad Airways | 21 | 2026-06-11 |
| ETD6PX | - | 19 | 2026-06-11 |
| ETD2NL | - | 17 | 2026-07-20 |
| ETD91N | - | 15 | 2026-07-19 |
| ETD13 | Etihad Airways | 14 | 2026-05-30 |
| ETD93C | Etihad Airways | 10 | 2026-07-25 |
| ETD16 | Etihad Airways | 10 | 2026-07-23 |
| ETD125 | Etihad Airways | 10 | 2026-07-21 |
| ETD47B | Etihad Airways | 9 | 2026-07-22 |
| ETD99P | Etihad Airways | 8 | 2026-07-21 |
| ETD76T | Etihad Airways | 7 | 2026-07-26 |
| ETD67B | - | 7 | 2026-07-17 |
| ETD128 | - | 7 | 2026-07-17 |
| ETD870 | Etihad Airways | 6 | 2026-06-14 |
| ETD9SM | Etihad Airways | 5 | 2026-05-31 |
| ETD871 | Etihad Airways | 3 | 2026-06-14 |
| ETD801 | Etihad Airways | 3 | 2026-04-28 |
| ETD800 | Etihad Airways | 3 | 2026-04-27 |
| ETD7EE | Etihad Airways | 3 | 2026-07-19 |
| ETD4RL | Etihad Airways | 3 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ETD76T | ORD → AUH | Jul 26, 19:10 UTC | Jul 26, 20:30 UTC | 1h 20m |
| 2026-07-25 | ETD93C | AUH → ORD | Jul 25, 23:20 UTC | Jul 26, 12:40 UTC | 13h 21m |
| 2026-07-25 | ETD358 | AUH → HYD | Jul 25, 12:20 UTC | Jul 25, 19:00 UTC | 6h 40m |
| 2026-07-25 | ETD358 | AUH → HYD | Jul 25, 11:00 UTC | Jul 25, 11:20 UTC | 20m |
| 2026-07-24 | ETD76T | ORD → AUH | Jul 24, 19:35 UTC | Jul 25, 08:20 UTC | 12h 45m |
| 2026-07-23 | ETD93C | AUH → ORD | Jul 23, 23:20 UTC | Jul 24, 13:40 UTC | 14h 20m |
| 2026-07-23 | ETD217 | BLR → AUH | Jul 23, 15:55 UTC | Jul 23, 18:40 UTC | 2h 45m |
| 2026-07-23 | ETD216 | AUH → DEL | Jul 23, 10:35 UTC | Jul 23, 13:45 UTC | 3h 10m |
| 2026-07-23 | ETD16 | MAN → AUH | Jul 23, 07:10 UTC | Jul 23, 08:10 UTC | 1h 0m |
| 2026-07-22 | ETD16 | MAN → AUH | Jul 22, 19:20 UTC | Jul 23, 06:10 UTC | 10h 50m |
| 2026-07-22 | ETD47B | AUH → CLT | Jul 22, 02:15 UTC | Jul 22, 14:15 UTC | 12h 0m |
| 2026-07-21 | ETD99P | MUC → AUH | Jul 21, 09:25 UTC | Jul 21, 15:50 UTC | 6h 25m |
| 2026-07-21 | ETD125 | AUH → MUC | Jul 21, 00:40 UTC | Jul 21, 06:45 UTC | 6h 5m |
| 2026-07-20 | ETD2NL | - | Jul 20, 08:25 UTC | Jul 20, 21:45 UTC | 13h 20m |
| 2026-07-19 | ETD91N | AUH → MEL | Jul 19, 17:35 UTC | Jul 20, 06:25 UTC | 12h 50m |
| 2026-07-19 | ETD7EE | ORD → AUH | Jul 19, 02:20 UTC | Jul 19, 15:25 UTC | 13h 5m |
| 2026-07-18 | ETD4RL | AUH → ORD | Jul 18, 06:50 UTC | Jul 18, 20:50 UTC | 14h 0m |
| 2026-07-17 | ETD128 | - | Jul 17, 20:50 UTC | Jul 18, 02:25 UTC | 5h 35m |
| 2026-07-17 | ETD67B | - | Jul 17, 12:04 UTC | Jul 17, 17:40 UTC | 5h 35m |
| 2026-07-16 | ETD76T | ORD → AUH | Jul 16, 19:30 UTC | Jul 17, 08:25 UTC | 12h 55m |
| 2026-07-16 | ETD93C | - | Jul 16, 00:15 UTC | Jul 16, 14:10 UTC | 13h 55m |
| 2026-07-15 | ETD7EE | - | Jul 15, 01:50 UTC | Jul 15, 15:05 UTC | 13h 15m |
| 2026-07-14 | ETD4RL | - | Jul 14, 06:20 UTC | Jul 14, 20:35 UTC | 14h 15m |
| 2026-07-13 | ETD128 | - | Jul 13, 20:40 UTC | Jul 14, 02:10 UTC | 5h 30m |
| 2026-07-13 | ETD67B | - | Jul 13, 11:20 UTC | Jul 13, 17:25 UTC | 6h 5m |
| 2026-07-12 | ETD16 | - | Jul 12, 19:50 UTC | Jul 13, 08:55 UTC | 13h 5m |
| 2026-07-12 | ETD47B | - | Jul 12, 01:05 UTC | Jul 12, 15:15 UTC | 14h 10m |
| 2026-07-11 | ETD7EE | - | Jul 11, 02:05 UTC | Jul 11, 15:10 UTC | 13h 5m |
| 2026-07-10 | ETD4RL | - | Jul 10, 07:20 UTC | Jul 10, 21:05 UTC | 13h 46m |
| 2026-07-10 | ETD18M | - | Jul 10, 00:55 UTC | Jul 10, 01:45 UTC | 50m |
| 2026-07-09 | ETD18M | - | Jul 9, 20:10 UTC | Jul 9, 23:50 UTC | 3h 40m |
| 2026-07-09 | ETD123 | AUH → FRA | Jul 9, 11:15 UTC | Jul 9, 17:25 UTC | 6h 10m |
| 2026-07-08 | ETD16 | - | Jul 8, 19:35 UTC | Jul 9, 08:50 UTC | 13h 15m |
| 2026-07-08 | ETD47B | - | Jul 8, 00:20 UTC | Jul 8, 14:25 UTC | 14h 5m |
| 2026-07-07 | ETD2NL | MEL → AUH | Jul 7, 08:15 UTC | Jul 7, 21:05 UTC | 12h 50m |
| 2026-07-06 | ETD91N | - | Jul 6, 17:25 UTC | Jul 7, 05:55 UTC | 12h 30m |
| 2026-07-05 | ETD16 | - | Jul 5, 20:15 UTC | Jul 6, 08:55 UTC | 12h 40m |
| 2026-07-05 | ETD47B | - | Jul 5, 00:20 UTC | Jul 5, 14:25 UTC | 14h 5m |
| 2026-07-04 | ETD4EH | - | Jul 4, 20:20 UTC | Jul 4, 20:50 UTC | 30m |
| 2026-07-04 | ETD8PF | - | Jul 4, 17:15 UTC | Jul 4, 17:25 UTC | 10m |
| 2026-07-03 | ETD16 | - | Jul 3, 20:20 UTC | Jul 4, 09:00 UTC | 12h 40m |
| 2026-07-03 | ETD47B | - | Jul 3, 00:10 UTC | Jul 3, 14:10 UTC | 14h 0m |
| 2026-07-01 | ETD16 | - | Jul 1, 20:35 UTC | Jul 2, 08:30 UTC | 11h 55m |
| 2026-07-01 | ETD16 | - | Jul 1, 19:25 UTC | Jul 1, 20:25 UTC | 1h 0m |
| 2026-07-01 | ETD47B | - | Jul 1, 11:35 UTC | Jul 1, 13:55 UTC | 2h 20m |
| 2026-07-01 | ETD47B | - | Jul 1, 00:00 UTC | Jul 1, 11:30 UTC | 11h 30m |
| 2026-06-30 | ETD359 | HYD → AUH | Jun 30, 10:50 UTC | Jun 30, 19:10 UTC | 8h 20m |
| 2026-06-29 | ETD76T | - | Jun 29, 19:35 UTC | Jun 30, 08:35 UTC | 13h 1m |
| 2026-06-28 | ETD93C | AUH → ORD | Jun 28, 23:25 UTC | Jun 29, 13:00 UTC | 13h 35m |
| 2026-06-28 | ETD358 | - | Jun 28, 10:39 UTC | Jun 28, 18:59 UTC | 8h 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-BNI page for operator, model, and routing details .