Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

896642

ICAO 24-bit transponder address · allocated to United Arab Emirates

Currently assigned to A6-FQD · BOEING 737 MAX 8

Hex
896642
Octal
42263102
Decimal
9,004,610
Country
AE
Tail
A6-FQD
Type
B38M
No current signal · last broadcast 1h ago
Flights observed
225
Distinct callsigns
20
Country
AE
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 896642.

Country allocation

The ICAO 24-bit address 896642 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
FDB9CE - 17 2026-07-14
FDB1595 - 15 2026-07-11
FDB910 - 13 2026-07-10
FDB1596 - 13 2026-07-11
FDB74X - 12 2026-07-14
FDB569 - 11 2026-07-10
FDB501 - 11 2026-06-14
FDB570 - 10 2026-07-10
FDB523 - 10 2026-06-29
FDB564 - 9 2026-06-28
FDB524 Fly Dubai 9 2026-06-29
FDB563 Fly Dubai 8 2026-06-27
FDB391 - 8 2026-07-12
FDB648 - 7 2026-07-14
FDB502 - 7 2026-06-15
FDB392 - 6 2026-07-12
FDB1JC - 6 2026-06-26
FDB75Y - 5 2026-06-27
FDB9JE - 3 2026-06-30
FDB909 - 3 2026-06-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB648 - Jul 14, 12:25 UTCJul 14, 21:40 UTC9h 15m
2026-07-14 FDB74X - Jul 14, 06:35 UTCJul 14, 06:40 UTC5m
2026-07-14 FDB9CE - Jul 14, 04:55 UTCJul 14, 05:10 UTC15m
2026-07-14 FDB9CE - Jul 14, 02:45 UTCJul 14, 03:10 UTC25m
2026-07-13 FDB2HR - Jul 13, 02:55 UTCJul 13, 08:01 UTC5h 5m
2026-07-12 FDB392 - Jul 12, 06:40 UTCJul 12, 09:15 UTC2h 35m
2026-07-12 FDB391 - Jul 12, 02:35 UTCJul 12, 04:50 UTC2h 15m
2026-07-11 FDB1596 - Jul 11, 16:05 UTCJul 11, 18:30 UTC2h 25m
2026-07-11 FDB1595 - Jul 11, 11:15 UTCJul 11, 12:10 UTC55m
2026-07-11 FDB1595 - Jul 11, 09:05 UTCJul 11, 09:30 UTC25m
2026-07-10 FDB570 - Jul 10, 20:55 UTCJul 11, 00:35 UTC3h 40m
2026-07-10 FDB569 - Jul 10, 15:15 UTCJul 10, 19:15 UTC4h 0m
2026-07-10 FDB910 - Jul 10, 06:15 UTCJul 10, 12:45 UTC6h 30m
2026-07-05 FDB812 - Jul 5, 12:20 UTCJul 5, 18:25 UTC6h 5m
2026-07-05 FDB392 - Jul 5, 06:40 UTCJul 5, 09:05 UTC2h 25m
2026-07-05 FDB391 - Jul 5, 02:30 UTCJul 5, 04:40 UTC2h 10m
2026-07-04 FDB910 - Jul 4, 06:20 UTCJul 4, 13:10 UTC6h 50m
2026-07-03 FDB570 - Jul 3, 21:10 UTCJul 4, 01:20 UTC4h 10m
2026-07-03 FDB569 DXB → CMB Jul 3, 15:15 UTCJul 3, 19:10 UTC3h 55m
2026-07-03 FDB910 - Jul 3, 06:35 UTCJul 3, 12:55 UTC6h 20m
2026-07-02 FDB570 - Jul 2, 21:00 UTCJul 3, 00:55 UTC3h 55m
2026-07-02 FDB569 DXB → CMB Jul 2, 17:00 UTCJul 2, 19:05 UTC2h 5m
2026-07-02 FDB569 DXB → CMB Jul 2, 15:10 UTCJul 2, 15:40 UTC30m
2026-07-02 FDB74X - Jul 2, 08:30 UTCJul 2, 09:00 UTC30m
2026-07-02 FDB74X - Jul 2, 06:35 UTCJul 2, 06:41 UTC6m
2026-07-02 FDB9CE - Jul 2, 05:00 UTCJul 2, 05:10 UTC10m
2026-07-02 FDB9CE - Jul 2, 02:50 UTCJul 2, 03:20 UTC30m
2026-07-01 FDB648 ADD → DXB Jul 1, 11:55 UTCJul 1, 21:50 UTC9h 55m
2026-07-01 FDB74X - Jul 1, 08:20 UTCJul 1, 08:45 UTC25m
2026-07-01 FZ74X - Jul 1, 06:25 UTCJul 1, 06:30 UTC5m
2026-07-01 FDB9CE - Jul 1, 05:00 UTCJul 1, 05:10 UTC10m
2026-07-01 FDB9CE - Jul 1, 02:50 UTCJul 1, 03:20 UTC30m
2026-06-30 FDB647 DXB → ADD Jun 30, 11:50 UTCJun 30, 21:50 UTC10h 0m
2026-06-30 FDB9JE - Jun 30, 08:35 UTCJun 30, 09:05 UTC30m
2026-06-30 FDB1KX - Jun 30, 02:10 UTCJun 30, 06:55 UTC4h 45m
2026-06-29 FDB524 DAC → DXB Jun 29, 16:29 UTCJun 29, 20:59 UTC4h 30m
2026-06-29 FDB523 - Jun 29, 10:20 UTCJun 29, 14:50 UTC4h 30m
2026-06-28 FDB564 - Jun 28, 04:29 UTCJun 28, 09:05 UTC4h 35m
2026-06-27 FDB563 DXB → CGP Jun 27, 22:15 UTCJun 28, 02:44 UTC4h 30m
2026-06-27 FDB550 CMB → DXB Jun 27, 12:39 UTCJun 27, 16:24 UTC3h 45m
2026-06-27 FDB549 DXB → CMB Jun 27, 06:40 UTCJun 27, 10:40 UTC4h 0m
2026-06-27 FDB75Y - Jun 27, 00:34 UTCJun 27, 01:04 UTC30m
2026-06-26 FDB75Y - Jun 26, 22:44 UTCJun 26, 22:49 UTC5m
2026-06-26 FDB1JC - Jun 26, 21:20 UTCJun 26, 21:30 UTC10m
2026-06-26 FDB1JC - Jun 26, 19:09 UTCJun 26, 19:39 UTC30m
2026-06-26 FDB74X - Jun 26, 08:24 UTCJun 26, 08:54 UTC30m
2026-06-26 FDB74X - Jun 26, 06:35 UTCJun 26, 06:39 UTC5m
2026-06-26 FDB9CE - Jun 26, 04:55 UTCJun 26, 05:10 UTC15m
2026-06-26 FDB9CE - Jun 26, 02:50 UTCJun 26, 03:15 UTC25m
2026-06-25 FDB876 TIF → DXB Jun 25, 13:14 UTCJun 25, 18:15 UTC5h 0m

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-FQD page for operator, model, and routing details .

Mode-S 896642 frequently asked

What is Mode-S code 896642?
896642 is an ICAO 24-bit transponder address. Allocated to United Arab Emirates. Assigned to A6-FQD.
Where is Mode-S 896642 registered?
Mode-S code 896642 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 896642 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 896642, octal 42263102, decimal 9,004,610.
What flights does 896642 operate?
Mode-S 896642 has broadcast 20 distinct callsigns, including FDB9CE, FDB1595, FDB910, FDB1596, FDB74X.