Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

896663

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

Currently assigned to A6-FQJ · BOEING 737 MAX 8

Hex
896663
Octal
42263143
Decimal
9,004,643
Country
AE
Tail
A6-FQJ
Type
B38M
No current signal · last broadcast 13h ago
Flights observed
212
Distinct callsigns
20
Country
AE
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 896663.

Country allocation

The ICAO 24-bit address 896663 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
FDB1596 - 13 2026-07-12
FDB1595 - 12 2026-07-12
FDB549 - 11 2026-07-09
FDB502 - 11 2026-07-04
FDB9CE - 10 2026-07-13
FDB501 - 10 2026-07-03
FDB569 Fly Dubai 9 2026-06-26
FDB524 Fly Dubai 9 2026-07-05
FDB74X - 7 2026-07-13
FDB570 - 6 2026-06-26
FDB563 - 6 2026-07-14
FDB550 - 6 2026-07-09
FDB523 - 6 2026-07-05
FDB564 - 5 2026-07-14
FDB4DT Fly Dubai 5 2026-06-30
FDB9FX - 4 2026-06-30
FDB910 - 4 2026-06-27
FDB75Y - 4 2026-07-09
FDB540 Fly Dubai 4 2026-05-18
FDB1JC - 4 2026-07-08

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB564 - Jul 14, 04:50 UTCJul 14, 07:45 UTC2h 55m
2026-07-14 FDB563 - Jul 14, 00:00 UTCJul 14, 03:00 UTC3h 0m
2026-07-13 FDB563 - Jul 13, 22:25 UTCJul 13, 22:50 UTC25m
2026-07-13 FDB74X - Jul 13, 08:20 UTCJul 13, 08:50 UTC30m
2026-07-13 FDB74X - Jul 13, 06:30 UTCJul 13, 06:35 UTC5m
2026-07-13 FDB9CE - Jul 13, 05:05 UTCJul 13, 05:10 UTC5m
2026-07-13 FDB9CE - Jul 13, 02:50 UTCJul 13, 03:15 UTC25m
2026-07-12 FDB1596 - Jul 12, 15:01 UTCJul 12, 19:05 UTC4h 5m
2026-07-12 FDB1595 - Jul 12, 10:55 UTCJul 12, 12:45 UTC1h 50m
2026-07-11 FDB641 - Jul 11, 21:10 UTCJul 12, 06:15 UTC9h 5m
2026-07-11 FDB898 - Jul 11, 10:55 UTCJul 11, 17:00 UTC6h 5m
2026-07-10 FDB1596 - Jul 10, 18:20 UTCJul 10, 18:45 UTC25m
2026-07-10 FDB1596 - Jul 10, 16:30 UTCJul 10, 17:15 UTC45m
2026-07-10 FDB1595 - Jul 10, 09:10 UTCJul 10, 12:20 UTC3h 10m
2026-07-10 FDB642 - Jul 10, 06:10 UTCJul 10, 06:35 UTC25m
2026-07-09 FDB550 - Jul 9, 12:35 UTCJul 9, 14:30 UTC1h 55m
2026-07-09 FDB549 - Jul 9, 08:25 UTCJul 9, 10:35 UTC2h 10m
2026-07-09 FDB549 - Jul 9, 06:35 UTCJul 9, 07:00 UTC25m
2026-07-09 FDB75Y - Jul 9, 00:20 UTCJul 9, 00:30 UTC10m
2026-07-08 FDB75Y - Jul 8, 22:05 UTCJul 8, 22:10 UTC5m
2026-07-08 FDB1JC - Jul 8, 20:45 UTCJul 8, 20:55 UTC10m
2026-07-08 FDB308 - Jul 8, 15:15 UTCJul 8, 15:40 UTC25m
2026-07-08 FDB307 - Jul 8, 08:20 UTCJul 8, 08:45 UTC25m
2026-07-07 FDB830 JED → DXB Jul 7, 11:15 UTCJul 7, 17:35 UTC6h 20m
2026-07-07 FDB1KX - Jul 7, 02:00 UTCJul 7, 06:45 UTC4h 45m
2026-07-06 FDB898 - Jul 6, 10:45 UTCJul 6, 16:45 UTC6h 0m
2026-07-05 FDB524 DAC → DXB Jul 5, 19:00 UTCJul 5, 23:25 UTC4h 25m
2026-07-05 FDB523 - Jul 5, 10:25 UTCJul 5, 15:00 UTC4h 35m
2026-07-05 FDB2HR - Jul 5, 03:00 UTCJul 5, 08:25 UTC5h 25m
2026-07-04 FDB524 DAC → DXB Jul 4, 20:35 UTCJul 4, 21:05 UTC30m
2026-07-04 FDB524 DAC → DXB Jul 4, 16:30 UTCJul 4, 19:30 UTC3h 0m
2026-07-04 FDB523 - Jul 4, 14:00 UTCJul 4, 15:05 UTC1h 5m
2026-07-04 FDB523 - Jul 4, 10:30 UTCJul 4, 10:55 UTC25m
2026-07-04 FDB502 - Jul 4, 03:00 UTCJul 4, 07:30 UTC4h 30m
2026-07-03 FDB501 - Jul 3, 20:50 UTCJul 4, 01:20 UTC4h 30m
2026-07-03 FDB550 - Jul 3, 12:50 UTCJul 3, 16:20 UTC3h 30m
2026-07-03 FDB549 - Jul 3, 06:35 UTCJul 3, 10:25 UTC3h 50m
2026-07-01 FDB898 - Jul 1, 10:45 UTCJul 1, 16:35 UTC5h 50m
2026-06-30 FDB4DT DXB → SKT Jun 30, 20:50 UTCJul 1, 03:50 UTC7h 0m
2026-06-30 FDB550 CMB → DXB Jun 30, 12:35 UTCJun 30, 16:15 UTC3h 40m
2026-06-30 FDB549 DXB → CMB Jun 30, 08:30 UTCJun 30, 10:35 UTC2h 5m
2026-06-30 FDB549 DXB → CMB Jun 30, 06:35 UTCJun 30, 06:55 UTC20m
2026-06-30 FDB9FX - Jun 30, 01:45 UTCJun 30, 04:05 UTC2h 20m
2026-06-29 FDB4DT DXB → SKT Jun 29, 21:05 UTCJun 29, 23:39 UTC2h 35m
2026-06-29 FDB550 CMB → DXB Jun 29, 12:20 UTCJun 29, 16:10 UTC3h 50m
2026-06-29 FDB549 DXB → CMB Jun 29, 06:34 UTCJun 29, 10:34 UTC4h 0m
2026-06-28 FDB524 DAC → DXB Jun 28, 20:14 UTCJun 28, 20:54 UTC40m
2026-06-28 FDB524 DAC → DXB Jun 28, 16:19 UTCJun 28, 19:14 UTC2h 55m
2026-06-28 FDB523 - Jun 28, 10:10 UTCJun 28, 14:39 UTC4h 30m
2026-06-27 FDB641 - Jun 27, 20:29 UTCJun 28, 06:05 UTC9h 35m

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

Mode-S 896663 frequently asked

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