sensors Mode-S transponder

89646C

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

Currently assigned to A6-FGE · BOEING 737-800

Hex
89646C
Octal
42262154
Decimal
9,004,140
Country
AE
Tail
A6-FGE
Type
B738
No current signal · last broadcast 3d ago
Flights observed
85
Distinct callsigns
20
Country
AE
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S 89646C.

Country allocation

The ICAO 24-bit address 89646C 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
FDB71T - 4 2026-07-02
FDB7ZK - 3 2026-07-12
FDB3YK - 3 2026-07-12
FDB1082 - 3 2026-07-06
FDB9RQ Fly Dubai 2 2026-04-27
FDB868 Fly Dubai 2 2026-07-01
FDB864 Fly Dubai 2 2026-06-04
FDB830 Fly Dubai 2 2026-06-26
FDB7XZ - 2 2026-07-11
FDB7AF - 2 2026-06-19
FDB5JA - 2 2026-07-12
FDB4RM - 2 2026-07-05
FDB3PM Fly Dubai 2 2026-04-17
FDB2WK - 2 2026-07-02
FDB2FL Fly Dubai 2 2026-06-20
FDB1ZA - 2 2026-07-05
FDB1081 - 2 2026-07-06
FDB1 Fly Dubai 2 2026-04-27
FDB94F - 1 2026-06-27
FDB9341 - 1 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB9341 - Jul 14, 14:05 UTCJul 14, 16:50 UTC2h 45m
2026-07-12 FDB7ZK - Jul 12, 16:10 UTCJul 12, 16:30 UTC20m
2026-07-12 FDB3YK - Jul 12, 13:30 UTCJul 12, 14:10 UTC40m
2026-07-12 FDB5WB - Jul 12, 07:25 UTCJul 12, 10:20 UTC2h 55m
2026-07-12 FDB5JA - Jul 12, 03:15 UTCJul 12, 04:05 UTC50m
2026-07-11 FDB7XZ - Jul 11, 06:20 UTCJul 11, 12:30 UTC6h 10m
2026-07-10 FDB7XZ - Jul 10, 06:55 UTCJul 10, 12:35 UTC5h 40m
2026-07-09 FDB821 - Jul 9, 10:00 UTCJul 10, 07:20 UTC21h 20m
2026-07-08 FDB733 - Jul 8, 13:35 UTCJul 8, 17:40 UTC4h 5m
2026-07-08 FDB5JA - Jul 8, 03:10 UTCJul 8, 11:15 UTC8h 5m
2026-07-06 FDB1082 - Jul 6, 13:05 UTCJul 6, 15:55 UTC2h 50m
2026-07-06 FDB1081 - Jul 6, 08:20 UTCJul 6, 11:20 UTC3h 0m
2026-07-05 FDB1ZA - Jul 5, 23:45 UTCJul 6, 02:15 UTC2h 30m
2026-07-05 FDB1ZA - Jul 5, 23:05 UTCJul 5, 23:40 UTC35m
2026-07-05 FDB4RM - Jul 5, 20:55 UTCJul 5, 21:20 UTC25m
2026-07-05 FDB4RM - Jul 5, 18:15 UTCJul 5, 19:15 UTC1h 0m
2026-07-05 FDB75L - Jul 5, 12:40 UTCJul 5, 13:30 UTC50m
2026-07-05 FDB15L - Jul 5, 11:00 UTCJul 5, 11:20 UTC20m
2026-07-04 FDB23L - Jul 4, 02:45 UTCJul 4, 09:20 UTC6h 35m
2026-07-03 FDB37M - Jul 3, 09:50 UTCJul 3, 12:45 UTC2h 55m
2026-07-02 FDB872 - Jul 2, 19:45 UTCJul 3, 00:15 UTC4h 30m
2026-07-02 FDB71T - Jul 2, 12:35 UTCJul 2, 16:10 UTC3h 35m
2026-07-02 FDB2WK - Jul 2, 07:45 UTCJul 2, 08:40 UTC55m
2026-07-01 FDB868 DMM → DXB Jul 1, 17:10 UTCJul 1, 18:05 UTC55m
2026-07-01 FDB867 - Jul 1, 15:10 UTCJul 1, 15:20 UTC10m
2026-07-01 FDB932 - Jul 1, 04:10 UTCJul 1, 10:55 UTC6h 45m
2026-06-30 FDB661 - Jun 30, 05:30 UTCJun 30, 12:55 UTC7h 25m
2026-06-29 FDB5YM DOH → DXB Jun 29, 14:19 UTCJun 29, 15:04 UTC45m
2026-06-29 FDB17 - Jun 29, 12:14 UTCJun 29, 12:55 UTC40m
2026-06-28 FDB3YX - Jun 28, 08:44 UTCJun 28, 13:34 UTC4h 50m
2026-06-27 FDB7ZK - Jun 27, 15:49 UTCJun 27, 16:35 UTC45m
2026-06-27 FDB3YK - Jun 27, 13:35 UTCJun 27, 14:20 UTC45m
2026-06-27 FDB5JN - Jun 27, 09:34 UTCJun 27, 09:55 UTC20m
2026-06-27 FDB94F - Jun 27, 07:19 UTCJun 27, 07:45 UTC25m
2026-06-26 FDB830 JED → DXB Jun 26, 11:20 UTCJun 26, 17:40 UTC6h 20m
2026-06-25 FDB830 JED → DXB Jun 25, 11:19 UTCJun 25, 18:00 UTC6h 40m
2026-06-24 FDB59K - Jun 24, 08:55 UTCJun 24, 13:50 UTC4h 55m
2026-06-22 FDB186 - Jun 22, 12:59 UTCJun 22, 16:29 UTC3h 30m
2026-06-22 FDB185 - Jun 22, 08:25 UTCJun 22, 11:44 UTC3h 20m
2026-06-21 FDB20 - Jun 21, 19:45 UTCJun 21, 20:14 UTC30m
2026-06-21 FDB928 - Jun 21, 06:44 UTCJun 21, 14:15 UTC7h 30m
2026-06-20 FDB2FL DXB → BGW Jun 20, 06:39 UTCJun 20, 07:29 UTC50m
2026-06-19 FDB7AF - Jun 19, 23:00 UTCJun 19, 23:39 UTC40m
2026-06-19 FDB441 - Jun 19, 20:24 UTCJun 19, 21:19 UTC55m
2026-06-19 FDB3DK - Jun 19, 07:54 UTCJun 19, 15:44 UTC7h 50m
2026-06-18 FDB43F - Jun 18, 16:00 UTCJun 18, 16:25 UTC25m
2026-06-18 FDB931 - Jun 18, 03:55 UTCJun 18, 10:30 UTC6h 35m
2026-06-17 FDB2FL DXB → BGW Jun 17, 06:05 UTCJun 17, 11:30 UTC5h 25m
2026-06-16 FDB2MF IST → DXB Jun 16, 15:55 UTCJun 16, 19:40 UTC3h 45m
2026-06-16 FDB4GP - Jun 16, 10:25 UTCJun 16, 14:05 UTC3h 40m

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

Mode-S 89646C frequently asked

What is Mode-S code 89646C?
89646C is an ICAO 24-bit transponder address. Allocated to United Arab Emirates. Assigned to A6-FGE.
Where is Mode-S 89646C registered?
Mode-S code 89646C 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 89646C broadcasting right now?
No active broadcast right now. Last signal was 3d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 89646C, octal 42262154, decimal 9,004,140.
What flights does 89646C operate?
Mode-S 89646C has broadcast 20 distinct callsigns, including FDB71T, FDB7ZK, FDB3YK, FDB1082, FDB9RQ.