sensors Mode-S transponder
896609
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKS · BOEING 737 MAX 8
- Hex
- 896609
- Octal
- 42263011
- Decimal
- 9,004,553
- Country
- AE
- Tail
- A6-FKS
- Type
- B38M
- Flights observed
- 54
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 896609 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 |
|---|---|---|---|
| FDB4DT | Fly Dubai | 5 | 2026-05-19 |
| FDB828 | Fly Dubai | 3 | 2026-05-26 |
| FDB818 | - | 2 | 2026-04-16 |
| FDB817 | Fly Dubai | 2 | 2026-04-16 |
| FDB810 | Fly Dubai | 2 | 2026-05-11 |
| FDB809 | Fly Dubai | 2 | 2026-04-13 |
| FDB64X | - | 2 | 2026-05-02 |
| FDB646 | Fly Dubai | 2 | 2026-05-06 |
| FDB4JZ | Fly Dubai | 2 | 2026-04-25 |
| FDB1AR | - | 2 | 2026-05-02 |
| FDB9RF | Fly Dubai | 1 | 2026-04-28 |
| FDB94F | Fly Dubai | 1 | 2026-04-20 |
| FDB906 | Fly Dubai | 1 | 2026-04-21 |
| FDB884 | Fly Dubai | 1 | 2026-05-10 |
| FDB882 | Fly Dubai | 1 | 2026-05-09 |
| FDB827 | Fly Dubai | 1 | 2026-04-23 |
| FDB812 | Fly Dubai | 1 | 2026-05-05 |
| FDB811 | Fly Dubai | 1 | 2026-05-05 |
| FDB7UE | Fly Dubai | 1 | 2026-05-23 |
| FDB71T | Fly Dubai | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | FDB828 | MED → DXB | May 26, 23:05 UTC | May 27, 12:50 UTC | 13h 46m |
| 2026-05-25 | FDB71T | TBS → DXB | May 25, 12:45 UTC | May 25, 16:30 UTC | 3h 45m |
| 2026-05-24 | FDB2WK | DXB → TBS | May 24, 23:00 UTC | May 25, 11:00 UTC | 12h 0m |
| 2026-05-24 | FDB828 | MED → DXB | May 24, 01:00 UTC | May 24, 23:20 UTC | 22h 20m |
| 2026-05-23 | FDB7UE | EVN → DXB | May 23, 11:35 UTC | May 24, 01:00 UTC | 13h 26m |
| 2026-05-22 | FDB828 | MED → DXB | May 22, 19:15 UTC | May 23, 07:05 UTC | 11h 49m |
| 2026-05-19 | FDB4DT | DXB → SKT | May 19, 22:25 UTC | May 19, 22:50 UTC | 25m |
| 2026-05-19 | FDB4DT | DXB → SKT | May 19, 01:20 UTC | May 19, 22:50 UTC | 21h 30m |
| 2026-05-18 | FDB4DT | DXB → SKT | May 18, 22:45 UTC | May 18, 23:10 UTC | 25m |
| 2026-05-11 | FDB810 | HOF → DXB | May 11, 12:55 UTC | May 11, 13:25 UTC | 30m |
| 2026-05-10 | FDB884 | DMM → DXB | May 10, 05:40 UTC | May 10, 06:40 UTC | 1h 0m |
| 2026-05-09 | FDB882 | TUU → DXB | May 9, 11:50 UTC | May 9, 17:30 UTC | 5h 40m |
| 2026-05-06 | FDB646 | ASM → DXB | May 6, 22:10 UTC | May 7, 15:45 UTC | 17h 36m |
| 2026-05-06 | FDB646 | ASM → DXB | May 6, 16:00 UTC | May 6, 22:45 UTC | 6h 44m |
| 2026-05-05 | FDB812 | AHB → DXB | May 5, 17:40 UTC | May 6, 16:10 UTC | 22h 30m |
| 2026-05-05 | FDB811 | DXB → AHB | May 5, 12:35 UTC | May 5, 18:05 UTC | 5h 30m |
| 2026-05-04 | FDB4DT | DXB → SKT | May 4, 22:40 UTC | May 5, 01:25 UTC | 2h 45m |
| 2026-05-04 | FDB4DT | DXB → SKT | May 4, 20:25 UTC | May 4, 20:50 UTC | 25m |
| 2026-05-04 | FDB2GT | KHI → DXB | May 4, 07:50 UTC | May 4, 08:20 UTC | 30m |
| 2026-05-04 | FDB1KF | DXB → KHI | May 4, 03:15 UTC | May 4, 03:35 UTC | 20m |
| 2026-05-03 | FDB662 | HGA → DXB | May 3, 07:35 UTC | May 3, 08:05 UTC | 30m |
| 2026-05-02 | FDB59J | BAH → DXB | May 2, 16:05 UTC | May 2, 17:00 UTC | 55m |
| 2026-05-02 | FDB5AY | DXB → BAH | May 2, 13:40 UTC | May 2, 14:35 UTC | 55m |
| 2026-05-02 | FDB64X | - | May 2, 09:25 UTC | May 2, 10:10 UTC | 45m |
| 2026-05-02 | FDB1AR | - | May 2, 07:05 UTC | May 2, 07:55 UTC | 50m |
| 2026-05-01 | FDB308 | KBL → DXB | May 1, 08:05 UTC | May 1, 15:30 UTC | 7h 25m |
| 2026-04-30 | FDB64X | - | Apr 30, 11:05 UTC | Apr 30, 12:00 UTC | 56m |
| 2026-04-30 | FDB1AR | - | Apr 30, 08:45 UTC | Apr 30, 09:35 UTC | 50m |
| 2026-04-28 | FDB454 | COK → DXB | Apr 28, 23:05 UTC | Apr 29, 02:40 UTC | 3h 35m |
| 2026-04-28 | FDB9RF | DXB → COK | Apr 28, 18:00 UTC | Apr 28, 21:25 UTC | 3h 25m |
| 2026-04-26 | FDB2UB | LYP → DXB | Apr 26, 01:35 UTC | Apr 26, 02:00 UTC | 25m |
| 2026-04-25 | FDB355 | DXB → LYP | Apr 25, 19:10 UTC | Apr 25, 19:30 UTC | 20m |
| 2026-04-25 | FDB1YT | BAH → DXB | Apr 25, 06:05 UTC | Apr 25, 07:30 UTC | 1h 25m |
| 2026-04-25 | FDB4JZ | DXB → BAH | Apr 25, 04:25 UTC | Apr 25, 04:40 UTC | 15m |
| 2026-04-25 | FDB4JZ | DXB → BAH | Apr 25, 02:20 UTC | Apr 25, 03:30 UTC | 1h 10m |
| 2026-04-24 | FDB5WB | BEY → DXB | Apr 24, 12:15 UTC | Apr 24, 15:25 UTC | 3h 10m |
| 2026-04-24 | FDB5JA | DXB → BEY | Apr 24, 07:10 UTC | Apr 24, 10:50 UTC | 3h 40m |
| 2026-04-23 | FDB827 | DXB → MED | Apr 23, 17:50 UTC | Apr 23, 23:55 UTC | 6h 5m |
| 2026-04-22 | FDB59K | KHI → DXB | Apr 22, 13:00 UTC | Apr 22, 13:25 UTC | 25m |
| 2026-04-22 | FDB3YX | DXB → KHI | Apr 22, 08:20 UTC | Apr 22, 08:40 UTC | 20m |
| 2026-04-21 | FDB906 | ULH → DXB | Apr 21, 15:51 UTC | Apr 21, 22:20 UTC | 6h 30m |
| 2026-04-20 | FDB5JN | MCT → DXB | Apr 20, 09:55 UTC | Apr 20, 10:25 UTC | 30m |
| 2026-04-20 | FDB94F | DXB → MCT | Apr 20, 07:25 UTC | Apr 20, 07:50 UTC | 25m |
| 2026-04-18 | FDB446 | BOM → DXB | Apr 18, 02:30 UTC | Apr 18, 03:05 UTC | 35m |
| 2026-04-17 | FDB445 | DXB → BOM | Apr 17, 19:45 UTC | Apr 17, 20:05 UTC | 20m |
| 2026-04-16 | FDB818 | - | Apr 16, 17:15 UTC | Apr 16, 17:25 UTC | 10m |
| 2026-04-16 | FDB818 | - | Apr 16, 16:15 UTC | Apr 16, 17:10 UTC | 55m |
| 2026-04-16 | FDB817 | DXB → YNB | Apr 16, 11:09 UTC | Apr 16, 11:49 UTC | 40m |
| 2026-04-16 | FDB817 | DXB → YNB | Apr 16, 10:40 UTC | Apr 16, 11:04 UTC | 25m |
| 2026-04-15 | FDB1114 | - | Apr 15, 14:05 UTC | Apr 15, 14:15 UTC | 10m |
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-FKS page for operator, model, and routing details .