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
Broadcasting now · callsign FDB5AY · 4,075 ft
Flights observed
154
Distinct callsigns
20
Country
AE
Last broadcast
5h ago

Current position

896609 is currently broadcasting. Map zoomed to live 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
FDB646 - 6 2026-07-13
FDB4DT Fly Dubai 5 2026-05-19
FDB828 - 4 2026-07-09
FDB64X Fly Dubai 4 2026-06-20
FDB4JZ - 4 2026-07-02
FDB3CK - 4 2026-07-09
FDB307 - 4 2026-07-12
FDB9GN - 3 2026-06-29
FDB811 - 3 2026-07-06
FDB7WG - 3 2026-07-02
FDB5EX - 3 2026-07-09
FDB1YT - 3 2026-07-02
FDB1AR Fly Dubai 3 2026-06-20
FDB9MF - 2 2026-07-03
FDB906 - 2 2026-06-25
FDB882 Fly Dubai 2 2026-07-05
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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB876 - Jul 14, 10:40 UTCJul 14, 15:40 UTC5h 0m
2026-07-13 FDB646 - Jul 13, 15:30 UTCJul 13, 23:05 UTC7h 35m
2026-07-13 FDB833 - Jul 13, 07:10 UTCJul 13, 13:50 UTC6h 40m
2026-07-12 FDB307 - Jul 12, 08:55 UTCJul 12, 15:55 UTC7h 0m
2026-07-12 FDB3UF - Jul 12, 05:40 UTCJul 12, 06:01 UTC20m
2026-07-12 FDB7HD - Jul 12, 03:15 UTCJul 12, 03:40 UTC25m
2026-07-11 FDB2PE - Jul 11, 15:25 UTCJul 11, 18:30 UTC3h 5m
2026-07-11 FDB39K - Jul 11, 11:25 UTCJul 11, 13:50 UTC2h 25m
2026-07-11 FDB1KF - Jul 11, 03:45 UTCJul 11, 08:35 UTC4h 50m
2026-07-10 FDB808 - Jul 10, 16:20 UTCJul 10, 22:55 UTC6h 35m
2026-07-10 FDB1848 - Jul 10, 10:45 UTCJul 10, 13:35 UTC2h 50m
2026-07-10 FDB1847 - Jul 10, 07:30 UTCJul 10, 09:15 UTC1h 45m
2026-07-09 FDB828 - Jul 9, 19:00 UTCJul 10, 00:20 UTC5h 20m
2026-07-09 FDB17 - Jul 9, 12:20 UTCJul 9, 12:55 UTC35m
2026-07-09 FDB3CK - Jul 9, 07:30 UTCJul 9, 10:15 UTC2h 45m
2026-07-09 FDB5EX - Jul 9, 03:05 UTCJul 9, 06:05 UTC3h 0m
2026-07-08 FDB646 ASM → DXB Jul 8, 15:35 UTCJul 8, 23:25 UTC7h 50m
2026-07-08 FDB1074 - Jul 8, 08:00 UTCJul 8, 11:20 UTC3h 20m
2026-07-08 FDB1073 - Jul 8, 02:25 UTCJul 8, 05:20 UTC2h 55m
2026-07-07 FDB1HE - Jul 7, 17:55 UTCJul 7, 21:15 UTC3h 20m
2026-07-07 FDB183 - Jul 7, 13:25 UTCJul 7, 16:45 UTC3h 20m
2026-07-07 FDB3CK - Jul 7, 07:05 UTCJul 7, 09:45 UTC2h 40m
2026-07-07 FDB5EX - Jul 7, 02:55 UTCJul 7, 05:45 UTC2h 50m
2026-07-06 FDB811 - Jul 6, 12:20 UTCJul 6, 18:15 UTC5h 55m
2026-07-06 FDB3XY - Jul 6, 06:05 UTCJul 6, 09:30 UTC3h 25m
2026-07-06 FDB5NZ - Jul 6, 01:40 UTCJul 6, 05:00 UTC3h 20m
2026-07-05 FDB882 TUU → DXB Jul 5, 11:25 UTCJul 5, 18:00 UTC6h 35m
2026-07-05 FDB3XY - Jul 5, 01:30 UTCJul 5, 09:25 UTC7h 55m
2026-07-04 FDB646 ASM → DXB Jul 4, 15:35 UTCJul 4, 23:20 UTC7h 45m
2026-07-04 FDB864 - Jul 4, 12:40 UTCJul 4, 13:40 UTC1h 0m
2026-07-04 FDB863 - Jul 4, 10:10 UTCJul 4, 10:55 UTC45m
2026-07-04 FDB9RQ - Jul 4, 07:20 UTCJul 4, 08:20 UTC1h 0m
2026-07-04 FDB1 - Jul 4, 05:10 UTCJul 4, 05:50 UTC40m
2026-07-03 FDB7XP - Jul 3, 13:35 UTCJul 3, 14:10 UTC35m
2026-07-03 FDB9MF - Jul 3, 10:10 UTCJul 3, 10:45 UTC35m
2026-07-03 FDB5PS - Jul 3, 02:15 UTCJul 3, 05:40 UTC3h 25m
2026-07-02 FDB7WG - Jul 2, 21:20 UTCJul 3, 00:40 UTC3h 20m
2026-07-02 FDB9MF - Jul 2, 09:45 UTCJul 2, 14:15 UTC4h 30m
2026-07-02 FDB1YT - Jul 2, 05:40 UTCJul 2, 06:30 UTC50m
2026-07-02 FDB4JZ - Jul 2, 03:25 UTCJul 2, 04:10 UTC45m
2026-07-01 FDB1HE - Jul 1, 17:35 UTCJul 1, 21:10 UTC3h 35m
2026-07-01 FDB183 - Jul 1, 13:35 UTCJul 1, 16:25 UTC2h 50m
2026-07-01 FDB1074 - Jul 1, 07:50 UTCJul 1, 10:40 UTC2h 50m
2026-07-01 FDB1073 DXB → TLV Jul 1, 02:25 UTCJul 1, 05:20 UTC2h 55m
2026-06-30 FDB308 - Jun 30, 10:00 UTCJun 30, 15:30 UTC5h 30m
2026-06-30 FDB307 - Jun 30, 07:50 UTCJun 30, 08:15 UTC25m
2026-06-30 FDB5JD - Jun 30, 01:25 UTCJun 30, 04:50 UTC3h 26m
2026-06-29 FDB4XC - Jun 29, 19:15 UTCJun 29, 22:49 UTC3h 35m
2026-06-29 FDB9GN - Jun 29, 12:00 UTCJun 29, 16:10 UTC4h 10m
2026-06-29 FDB5PS - Jun 29, 02:09 UTCJun 29, 05:54 UTC3h 45m

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 .

Mode-S 896609 frequently asked

What is Mode-S code 896609?
896609 is an ICAO 24-bit transponder address. Allocated to United Arab Emirates. Assigned to A6-FKS.
Where is Mode-S 896609 registered?
Mode-S code 896609 is allocated to United Arab Emirates (AE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 896609 broadcasting right now?
Yes. Mode-S 896609 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 896609, octal 42263011, decimal 9,004,553.
What flights does 896609 operate?
Mode-S 896609 has broadcast 20 distinct callsigns, including FDB646, FDB4DT, FDB828, FDB64X, FDB4JZ.