sensors Mode-S transponder
896689
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPH · BOEING 737 MAX 8
- Hex
- 896689
- Octal
- 42263211
- Decimal
- 9,004,681
- Country
- AE
- Tail
- A6-FPH
- Type
- B38M
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 896689 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 |
|---|---|---|---|
| FDB1689 | Fly Dubai | 7 | 2026-05-13 |
| FDB1690 | Fly Dubai | 6 | 2026-05-14 |
| FDB540 | Fly Dubai | 3 | 2026-04-23 |
| FDB539 | Fly Dubai | 3 | 2026-04-23 |
| FDB1502 | Fly Dubai | 3 | 2026-05-24 |
| FDB914 | Fly Dubai | 2 | 2026-04-16 |
| FDB864 | Fly Dubai | 2 | 2026-04-28 |
| FDB7UE | Fly Dubai | 2 | 2026-05-20 |
| FDB65E | Fly Dubai | 2 | 2026-04-27 |
| FDB5YA | Fly Dubai | 2 | 2026-05-09 |
| FDB4GP | - | 2 | 2026-04-13 |
| FDB3DK | Fly Dubai | 2 | 2026-05-27 |
| FDB2MF | Fly Dubai | 2 | 2026-04-13 |
| FDB1NU | Fly Dubai | 2 | 2026-05-26 |
| FDB1942 | Fly Dubai | 2 | 2026-05-28 |
| FDB1736 | Fly Dubai | 2 | 2026-05-01 |
| FDB1735 | Fly Dubai | 2 | 2026-04-30 |
| FDB9UR | - | 1 | 2026-04-13 |
| FDB9DV | Fly Dubai | 1 | 2026-05-28 |
| FDB989 | Fly Dubai | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB9DV | DXB → EBL | May 28, 14:25 UTC | May 29, 08:30 UTC | 18h 5m |
| 2026-05-28 | FDB1942 | TAS → DXB | May 28, 00:45 UTC | May 28, 14:30 UTC | 13h 45m |
| 2026-05-27 | FDB3DK | EBL → DXB | May 27, 14:10 UTC | May 28, 00:50 UTC | 10h 40m |
| 2026-05-27 | FDB3DK | EBL → DXB | May 27, 01:09 UTC | May 27, 14:50 UTC | 13h 40m |
| 2026-05-26 | FDB5GE | OTP → DXB | May 26, 06:44 UTC | May 27, 01:14 UTC | 18h 30m |
| 2026-05-26 | FDB1NU | DXB → OTP | May 26, 02:39 UTC | May 26, 05:05 UTC | 2h 25m |
| 2026-05-25 | FDB1NU | DXB → OTP | May 25, 09:45 UTC | May 26, 05:05 UTC | 19h 19m |
| 2026-05-24 | FDB1502 | CTA → DXB | May 24, 15:00 UTC | May 25, 09:45 UTC | 18h 45m |
| 2026-05-24 | FDB1502 | CTA → DXB | May 24, 12:25 UTC | May 25, 09:45 UTC | 21h 20m |
| 2026-05-24 | FDB1502 | CTA → DXB | May 24, 10:50 UTC | May 25, 09:45 UTC | 22h 55m |
| 2026-05-24 | FDB5HR | DXB → CTA | May 24, 05:35 UTC | May 24, 08:15 UTC | 2h 40m |
| 2026-05-22 | FDB1722 | ALA → DXB | May 22, 02:25 UTC | May 23, 01:20 UTC | 22h 55m |
| 2026-05-20 | FDB7UE | EVN → DXB | May 20, 08:45 UTC | May 20, 19:20 UTC | 10h 35m |
| 2026-05-14 | FDB1690 | FRU → DXB | May 14, 01:40 UTC | May 14, 16:10 UTC | 14h 30m |
| 2026-05-13 | FDB1689 | DXB → FRU | May 13, 17:50 UTC | May 13, 18:10 UTC | 20m |
| 2026-05-13 | FDB7XZ | BGW → DXB | May 13, 11:55 UTC | May 13, 12:25 UTC | 30m |
| 2026-05-09 | FDB5YA | VKO → DXB | May 9, 18:05 UTC | May 10, 07:10 UTC | 13h 5m |
| 2026-05-08 | FDB1114 | DAM → DXB | May 8, 02:09 UTC | May 8, 16:05 UTC | 13h 55m |
| 2026-05-04 | FDB4TB | DXB → VKO | May 4, 14:10 UTC | May 4, 14:35 UTC | 25m |
| 2026-05-03 | FDB1289 | DXB → MBA | May 3, 10:40 UTC | May 3, 21:54 UTC | 11h 15m |
| 2026-05-03 | FDB1690 | FRU → DXB | May 3, 01:50 UTC | May 3, 04:20 UTC | 2h 29m |
| 2026-05-02 | FDB1689 | DXB → FRU | May 2, 17:50 UTC | May 2, 18:15 UTC | 25m |
| 2026-05-01 | FDB1690 | FRU → DXB | May 1, 20:10 UTC | May 2, 04:20 UTC | 8h 10m |
| 2026-05-01 | FDB1689 | DXB → FRU | May 1, 18:10 UTC | May 1, 18:30 UTC | 20m |
| 2026-05-01 | FDB1736 | ALA → DXB | May 1, 04:20 UTC | May 1, 04:40 UTC | 20m |
| 2026-04-30 | FDB1735 | DXB → ALA | Apr 30, 18:25 UTC | May 1, 02:15 UTC | 7h 50m |
| 2026-04-30 | FDB915 | DXB → EAM | Apr 30, 09:40 UTC | Apr 30, 15:30 UTC | 5h 50m |
| 2026-04-29 | FDB1689 | DXB → FRU | Apr 29, 18:15 UTC | Apr 30, 04:25 UTC | 10h 9m |
| 2026-04-29 | FDB1736 | ALA → DXB | Apr 29, 02:24 UTC | Apr 29, 04:49 UTC | 2h 25m |
| 2026-04-28 | FDB1735 | DXB → ALA | Apr 28, 18:20 UTC | Apr 28, 18:40 UTC | 20m |
| 2026-04-28 | FDB864 | DMM → DXB | Apr 28, 12:55 UTC | Apr 28, 13:55 UTC | 1h 0m |
| 2026-04-28 | FDB863 | DXB → DMM | Apr 28, 08:50 UTC | Apr 28, 09:40 UTC | 50m |
| 2026-04-27 | FDB65E | EBB → DXB | Apr 27, 09:40 UTC | Apr 27, 21:35 UTC | 11h 55m |
| 2026-04-27 | FDB1690 | FRU → DXB | Apr 27, 03:25 UTC | Apr 27, 04:05 UTC | 40m |
| 2026-04-26 | FDB1689 | DXB → FRU | Apr 26, 18:05 UTC | Apr 26, 18:25 UTC | 20m |
| 2026-04-26 | FDB1690 | FRU → DXB | Apr 26, 03:30 UTC | Apr 26, 04:00 UTC | 30m |
| 2026-04-25 | FDB1689 | DXB → FRU | Apr 25, 18:05 UTC | Apr 25, 18:30 UTC | 25m |
| 2026-04-25 | FDB2DC | LHE → DXB | Apr 25, 03:05 UTC | Apr 25, 03:35 UTC | 30m |
| 2026-04-24 | FDB7SK | DXB → LHE | Apr 24, 20:30 UTC | Apr 24, 20:55 UTC | 25m |
| 2026-04-24 | FDB864 | DMM → DXB | Apr 24, 09:05 UTC | Apr 24, 14:15 UTC | 5h 10m |
| 2026-04-24 | FDB1690 | FRU → DXB | Apr 24, 03:50 UTC | Apr 24, 04:15 UTC | 25m |
| 2026-04-23 | FDB1689 | DXB → FRU | Apr 23, 18:05 UTC | Apr 23, 18:30 UTC | 25m |
| 2026-04-23 | FDB540 | KTM → DXB | Apr 23, 11:55 UTC | Apr 23, 15:25 UTC | 3h 30m |
| 2026-04-23 | FDB539 | DXB → KTM | Apr 23, 08:01 UTC | Apr 23, 08:45 UTC | 45m |
| 2026-04-23 | FDB539 | DXB → KTM | Apr 23, 05:30 UTC | Apr 23, 05:55 UTC | 25m |
| 2026-04-22 | FDB7KL | AMM → DXB | Apr 22, 21:15 UTC | Apr 22, 22:30 UTC | 1h 15m |
| 2026-04-22 | FDB143 | DXB → AMM | Apr 22, 14:30 UTC | Apr 22, 15:45 UTC | 1h 15m |
| 2026-04-22 | FDB794 | DYU → DXB | Apr 22, 03:05 UTC | Apr 22, 03:30 UTC | 25m |
| 2026-04-21 | FDB793 | DXB → DYU | Apr 21, 17:50 UTC | Apr 21, 18:10 UTC | 20m |
| 2026-04-20 | FDB1ZA | SPX → DXB | Apr 20, 23:20 UTC | Apr 21, 02:25 UTC | 3h 5m |
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-FPH page for operator, model, and routing details .