Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

896662

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

Currently assigned to A6-FQI · BOEING 737 MAX 8

Hex
896662
Octal
42263142
Decimal
9,004,642
Country
AE
Tail
A6-FQI
Type
B38M
No current signal · last broadcast 2h ago
Flights observed
216
Distinct callsigns
20
Country
AE
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 896662.

Country allocation

The ICAO 24-bit address 896662 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
FDB523 - 13 2026-07-09
FDB549 - 12 2026-07-13
FDB524 - 11 2026-07-09
FDB550 - 9 2026-07-13
FDB502 - 9 2026-07-14
FDB501 - 9 2026-07-13
FDB9CE Fly Dubai 8 2026-05-19
FDB570 - 7 2026-07-08
FDB1JC - 7 2026-06-24
FDB75Y - 6 2026-06-24
FDB574 Fly Dubai 6 2026-05-23
FDB569 Fly Dubai 6 2026-07-07
FDB1596 - 6 2026-06-17
FDB910 - 5 2026-07-01
FDB74X Fly Dubai 5 2026-05-14
FDB573 Fly Dubai 5 2026-05-09
FDB564 - 5 2026-07-07
FDB1595 - 5 2026-06-17
FDB9UR - 4 2026-07-12
FDB897 - 4 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB897 - Jul 14, 10:50 UTCJul 14, 11:40 UTC50m
2026-07-14 FDB502 - Jul 14, 08:55 UTCJul 14, 09:15 UTC20m
2026-07-14 FDB502 - Jul 14, 04:40 UTCJul 14, 07:35 UTC2h 55m
2026-07-13 FDB501 - Jul 13, 22:05 UTCJul 14, 02:40 UTC4h 35m
2026-07-13 FDB550 - Jul 13, 12:10 UTCJul 13, 15:50 UTC3h 40m
2026-07-13 FDB549 - Jul 13, 08:20 UTCJul 13, 10:20 UTC2h 0m
2026-07-13 FDB549 - Jul 13, 06:20 UTCJul 13, 06:45 UTC25m
2026-07-12 FDB9UR CCU → DXB Jul 12, 21:00 UTCJul 13, 01:10 UTC4h 10m
2026-07-12 FDB461 - Jul 12, 15:20 UTCJul 12, 19:40 UTC4h 20m
2026-07-11 FDB818 - Jul 11, 09:40 UTCJul 11, 16:10 UTC6h 30m
2026-07-11 FDB9FX - Jul 11, 04:25 UTCJul 11, 04:45 UTC20m
2026-07-10 FDB4DT - Jul 10, 22:00 UTCJul 11, 02:40 UTC4h 40m
2026-07-10 FDB898 - Jul 10, 11:30 UTCJul 10, 16:55 UTC5h 25m
2026-07-10 FDB346 - Jul 10, 07:55 UTCJul 10, 08:25 UTC30m
2026-07-10 FDB2HR - Jul 10, 03:00 UTCJul 10, 03:25 UTC25m
2026-07-09 FDB524 - Jul 9, 16:25 UTCJul 9, 19:15 UTC2h 50m
2026-07-09 FDB523 - Jul 9, 10:25 UTCJul 9, 14:55 UTC4h 30m
2026-07-09 FDB832 - Jul 9, 01:15 UTCJul 9, 07:55 UTC6h 40m
2026-07-08 FDB550 - Jul 8, 15:35 UTCJul 8, 19:05 UTC3h 30m
2026-07-08 FDB549 - Jul 8, 08:30 UTCJul 8, 12:30 UTC4h 0m
2026-07-08 FDB570 - Jul 8, 00:55 UTCJul 8, 01:05 UTC10m
2026-07-07 FDB569 DXB → CMB Jul 7, 15:15 UTCJul 7, 23:05 UTC7h 50m
2026-07-07 FDB564 - Jul 7, 05:20 UTCJul 7, 08:20 UTC3h 0m
2026-07-06 FDB563 DXB → CGP Jul 6, 22:05 UTCJul 7, 02:35 UTC4h 30m
2026-07-06 FDB550 - Jul 6, 12:15 UTCJul 6, 16:05 UTC3h 50m
2026-07-06 FDB549 - Jul 6, 06:30 UTCJul 6, 10:25 UTC3h 55m
2026-07-05 FDB647 - Jul 5, 12:25 UTCJul 5, 21:45 UTC9h 20m
2026-07-05 FDB564 - Jul 5, 05:05 UTCJul 5, 09:30 UTC4h 25m
2026-07-04 FDB563 DXB → CGP Jul 4, 22:25 UTCJul 5, 03:00 UTC4h 35m
2026-07-03 FDB947 - Jul 3, 07:30 UTCJul 3, 11:40 UTC4h 10m
2026-07-02 FDB437 - Jul 2, 19:55 UTCJul 3, 02:00 UTC6h 5m
2026-07-02 FDB550 - Jul 2, 12:50 UTCJul 2, 16:30 UTC3h 40m
2026-07-02 FDB549 - Jul 2, 06:51 UTCJul 2, 10:50 UTC3h 59m
2026-07-01 FDB9UR - Jul 1, 20:30 UTCJul 2, 00:45 UTC4h 15m
2026-07-01 FDB461 - Jul 1, 14:55 UTCJul 1, 19:05 UTC4h 10m
2026-07-01 FDB910 - Jul 1, 06:30 UTCJul 1, 13:05 UTC6h 35m
2026-06-30 FDB808 JED → DXB Jun 30, 16:15 UTCJun 30, 22:50 UTC6h 35m
2026-06-30 FDB2HR - Jun 30, 03:05 UTCJun 30, 08:45 UTC5h 40m
2026-06-29 FDB7KL AMM → DXB Jun 29, 19:35 UTCJun 29, 22:19 UTC2h 45m
2026-06-29 FDB143 - Jun 29, 17:55 UTCJun 29, 18:10 UTC15m
2026-06-29 FDB143 - Jun 29, 15:30 UTCJun 29, 16:19 UTC50m
2026-06-29 FDB392 - Jun 29, 06:24 UTCJun 29, 08:54 UTC2h 30m
2026-06-29 FDB391 - Jun 29, 02:30 UTCJun 29, 04:50 UTC2h 20m
2026-06-28 FDB550 CMB → DXB Jun 28, 13:10 UTCJun 28, 16:49 UTC3h 40m
2026-06-28 FDB549 DXB → CMB Jun 28, 06:59 UTCJun 28, 11:00 UTC4h 0m
2026-06-27 FDB818 - Jun 27, 09:50 UTCJun 27, 16:20 UTC6h 30m
2026-06-26 FDB642 - Jun 26, 20:34 UTCJun 27, 06:09 UTC9h 35m
2026-06-26 FDB346 - Jun 26, 02:50 UTCJun 26, 08:10 UTC5h 20m
2026-06-25 FDB910 - Jun 25, 06:35 UTCJun 25, 13:09 UTC6h 35m
2026-06-24 FDB75Y - Jun 24, 23:59 UTCJun 25, 00:29 UTC30m

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

Mode-S 896662 frequently asked

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