sensors Mode-S transponder
896409
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-BLD · BOEING 787-9 Dreamliner
- Hex
- 896409
- Octal
- 42262011
- Decimal
- 9,004,041
- Country
- AE
- Tail
- A6-BLD
- Type
- B789
- Flights observed
- 132
- Distinct callsigns
- 14
- Country
- AE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 896409 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ETD7NZ | Etihad Airways | 24 | 2026-06-07 |
| ETD3AG | Etihad Airways | 18 | 2026-06-07 |
| ETD11B | Etihad Airways | 16 | 2026-06-12 |
| ETD69W | Etihad Airways | 15 | 2026-06-11 |
| ETD88C | Etihad Airways | 13 | 2026-06-11 |
| ETD8NY | Etihad Airways | 12 | 2026-06-09 |
| ETD498 | Etihad Airways | 12 | 2026-05-29 |
| ETD499 | Etihad Airways | 9 | 2026-06-10 |
| ETD332 | Etihad Airways | 4 | 2026-04-30 |
| ETD8KP | Etihad Airways | 2 | 2026-04-17 |
| ETD7QB | Etihad Airways | 2 | 2026-04-28 |
| ETD597 | Etihad Airways | 2 | 2026-04-28 |
| ETD12G | Etihad Airways | 2 | 2026-04-30 |
| ETD551 | Etihad Airways | 1 | 2026-04-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | ETD11B | AUH → JFK | Jun 12, 10:10 UTC | Jun 12, 19:50 UTC | 9h 40m |
| 2026-06-11 | ETD88C | LHR → AUH | Jun 11, 20:25 UTC | Jun 12, 02:30 UTC | 6h 5m |
| 2026-06-11 | ETD69W | AUH → LHR | Jun 11, 11:00 UTC | Jun 11, 14:30 UTC | 3h 30m |
| 2026-06-10 | ETD69W | AUH → LHR | Jun 10, 16:45 UTC | Jun 11, 14:30 UTC | 21h 45m |
| 2026-06-10 | ETD499 | SIN → AUH | Jun 10, 13:30 UTC | Jun 11, 12:15 UTC | 22h 45m |
| 2026-06-09 | ETD8NY | JFK → AUH | Jun 9, 08:05 UTC | Jun 10, 01:30 UTC | 17h 25m |
| 2026-06-09 | ETD8NY | JFK → AUH | Jun 9, 04:20 UTC | Jun 10, 01:30 UTC | 21h 10m |
| 2026-06-09 | ETD8NY | JFK → AUH | Jun 9, 03:10 UTC | Jun 10, 01:30 UTC | 22h 20m |
| 2026-06-08 | ETD11B | AUH → JFK | Jun 8, 09:30 UTC | Jun 8, 19:50 UTC | 10h 20m |
| 2026-06-07 | ETD3AG | CDG → AUH | Jun 7, 20:10 UTC | Jun 8, 02:00 UTC | 5h 50m |
| 2026-06-07 | ETD7NZ | AUH → CDG | Jun 7, 13:00 UTC | Jun 7, 17:35 UTC | 4h 35m |
| 2026-06-06 | ETD3AG | CDG → AUH | Jun 6, 23:39 UTC | Jun 7, 01:40 UTC | 2h 0m |
| 2026-06-06 | ETD3AG | CDG → AUH | Jun 6, 20:05 UTC | Jun 6, 23:35 UTC | 3h 30m |
| 2026-06-06 | ETD7NZ | AUH → CDG | Jun 6, 13:44 UTC | Jun 6, 17:49 UTC | 4h 5m |
| 2026-06-05 | ETD7NZ | AUH → CDG | Jun 5, 18:20 UTC | Jun 6, 17:49 UTC | 23h 30m |
| 2026-06-05 | ETD7NZ | AUH → CDG | Jun 5, 18:00 UTC | Jun 6, 16:14 UTC | 22h 15m |
| 2026-06-05 | ETD499 | SIN → AUH | Jun 5, 13:40 UTC | Jun 5, 18:25 UTC | 4h 45m |
| 2026-06-04 | ETD8NY | JFK → AUH | Jun 4, 07:40 UTC | Jun 5, 01:45 UTC | 18h 5m |
| 2026-06-04 | ETD8NY | JFK → AUH | Jun 4, 02:40 UTC | Jun 5, 01:45 UTC | 23h 5m |
| 2026-06-03 | ETD11B | AUH → JFK | Jun 3, 00:20 UTC | Jun 3, 19:30 UTC | 19h 10m |
| 2026-06-02 | ETD11B | AUH → JFK | Jun 2, 22:20 UTC | Jun 3, 19:30 UTC | 21h 10m |
| 2026-06-02 | ETD11B | AUH → JFK | Jun 2, 20:20 UTC | Jun 3, 19:30 UTC | 23h 10m |
| 2026-06-02 | ETD7NZ | AUH → CDG | Jun 2, 11:30 UTC | Jun 2, 17:30 UTC | 6h 0m |
| 2026-06-01 | ETD3AG | CDG → AUH | Jun 1, 20:05 UTC | Jun 2, 01:45 UTC | 5h 40m |
| 2026-06-01 | ETD7NZ | AUH → CDG | Jun 1, 13:10 UTC | Jun 1, 17:45 UTC | 4h 35m |
| 2026-05-30 | ETD499 | SIN → AUH | May 30, 13:20 UTC | May 30, 18:05 UTC | 4h 45m |
| 2026-05-29 | ETD498 | AUH → SIN | May 29, 20:20 UTC | May 30, 01:30 UTC | 5h 10m |
| 2026-05-29 | ETD8NY | JFK → AUH | May 29, 03:00 UTC | May 29, 14:55 UTC | 11h 55m |
| 2026-05-28 | ETD11B | AUH → JFK | May 28, 09:40 UTC | May 28, 19:25 UTC | 9h 45m |
| 2026-05-27 | ETD11B | AUH → JFK | May 27, 16:45 UTC | May 28, 14:00 UTC | 21h 15m |
| 2026-05-27 | ETD11B | AUH → JFK | May 27, 13:20 UTC | May 28, 12:15 UTC | 22h 55m |
| 2026-05-26 | ETD498 | AUH → SIN | May 26, 20:15 UTC | May 27, 01:24 UTC | 5h 10m |
| 2026-05-26 | ETD8NY | JFK → AUH | May 26, 03:00 UTC | May 26, 14:50 UTC | 11h 50m |
| 2026-05-25 | ETD11B | AUH → JFK | May 25, 06:10 UTC | May 25, 19:25 UTC | 13h 14m |
| 2026-05-24 | ETD499 | SIN → AUH | May 24, 13:30 UTC | May 24, 19:45 UTC | 6h 15m |
| 2026-05-23 | ETD498 | AUH → SIN | May 23, 20:15 UTC | May 24, 01:15 UTC | 5h 0m |
| 2026-05-23 | ETD8NY | JFK → AUH | May 23, 02:35 UTC | May 23, 14:10 UTC | 11h 35m |
| 2026-05-22 | ETD11B | AUH → JFK | May 22, 10:15 UTC | May 22, 20:00 UTC | 9h 45m |
| 2026-05-21 | ETD11B | AUH → JFK | May 21, 16:35 UTC | May 22, 14:20 UTC | 21h 45m |
| 2026-05-21 | ETD11B | AUH → JFK | May 21, 13:30 UTC | May 22, 12:15 UTC | 22h 45m |
| 2026-05-20 | ETD8NY | JFK → AUH | May 20, 08:50 UTC | May 21, 00:50 UTC | 16h 0m |
| 2026-05-20 | ETD8NY | JFK → AUH | May 20, 03:30 UTC | May 21, 00:50 UTC | 21h 21m |
| 2026-05-19 | ETD11B | AUH → JFK | May 19, 06:20 UTC | May 19, 19:50 UTC | 13h 30m |
| 2026-05-11 | ETD88C | LHR → AUH | May 11, 20:10 UTC | May 11, 22:35 UTC | 2h 24m |
| 2026-05-11 | ETD69W | AUH → LHR | May 11, 09:50 UTC | May 11, 14:30 UTC | 4h 40m |
| 2026-05-10 | ETD88C | LHR → AUH | May 10, 20:14 UTC | May 11, 02:20 UTC | 6h 5m |
| 2026-05-10 | ETD69W | AUH → LHR | May 10, 09:24 UTC | May 10, 14:09 UTC | 4h 45m |
| 2026-05-09 | ETD69W | AUH → LHR | May 9, 16:35 UTC | May 10, 14:09 UTC | 21h 35m |
| 2026-05-09 | ETD69W | AUH → LHR | May 9, 13:35 UTC | May 10, 12:15 UTC | 22h 40m |
| 2026-05-08 | ETD8NY | JFK → AUH | May 8, 08:09 UTC | May 9, 00:30 UTC | 16h 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-BLD page for operator, model, and routing details .