sensors Mode-S transponder
89660D
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FQC · BOEING 737 MAX 8
- Hex
- 89660D
- Octal
- 42263015
- Decimal
- 9,004,557
- Country
- AE
- Tail
- A6-FQC
- Type
- B38M
- Flights observed
- 110
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 89660D 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 | Fly Dubai | 10 | 2026-05-18 |
| FDB1595 | Fly Dubai | 8 | 2026-05-18 |
| FDB563 | Fly Dubai | 6 | 2026-05-20 |
| FDB909 | Fly Dubai | 5 | 2026-04-21 |
| FDB74X | Fly Dubai | 5 | 2026-05-05 |
| FDB564 | Fly Dubai | 5 | 2026-05-21 |
| FDB9CE | Fly Dubai | 4 | 2026-05-05 |
| FDB910 | Fly Dubai | 4 | 2026-04-17 |
| FDB828 | Fly Dubai | 4 | 2026-05-03 |
| FDB502 | Fly Dubai | 4 | 2026-05-30 |
| FDB501 | Fly Dubai | 4 | 2026-05-29 |
| FDB830 | Fly Dubai | 3 | 2026-05-28 |
| FDB807 | Fly Dubai | 3 | 2026-05-01 |
| FDB569 | Fly Dubai | 3 | 2026-05-13 |
| FDB524 | Fly Dubai | 3 | 2026-05-25 |
| FDB523 | Fly Dubai | 3 | 2026-05-19 |
| FDB392 | Fly Dubai | 3 | 2026-05-03 |
| FDB391 | Fly Dubai | 3 | 2026-05-10 |
| FDB8850 | Fly Dubai | 2 | 2026-05-23 |
| FDB827 | Fly Dubai | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB502 | DAC → DXB | May 30, 02:20 UTC | May 30, 05:35 UTC | 3h 15m |
| 2026-05-29 | FDB501 | DXB → DAC | May 29, 10:50 UTC | May 30, 00:55 UTC | 14h 5m |
| 2026-05-28 | FDB830 | JED → DXB | May 28, 16:05 UTC | May 29, 10:55 UTC | 18h 50m |
| 2026-05-27 | FDB876 | TIF → DXB | May 27, 17:25 UTC | May 28, 16:45 UTC | 23h 20m |
| 2026-05-27 | FDB5EX | DXB → AMM | May 27, 05:55 UTC | May 27, 06:15 UTC | 20m |
| 2026-05-25 | FDB524 | DAC → DXB | May 25, 16:25 UTC | May 26, 06:34 UTC | 14h 10m |
| 2026-05-25 | FDB502 | DAC → DXB | May 25, 02:25 UTC | May 25, 14:40 UTC | 12h 15m |
| 2026-05-24 | FDB830 | JED → DXB | May 24, 16:05 UTC | May 24, 16:40 UTC | 35m |
| 2026-05-23 | FDB830 | JED → DXB | May 23, 17:20 UTC | May 24, 16:40 UTC | 23h 20m |
| 2026-05-23 | FDB8850 | RUH → DXB | May 23, 11:45 UTC | May 23, 17:40 UTC | 5h 55m |
| 2026-05-22 | FDB8850 | RUH → DXB | May 22, 22:20 UTC | May 23, 17:40 UTC | 19h 20m |
| 2026-05-22 | FDB461 | DXB → CCU | May 22, 10:50 UTC | May 22, 18:40 UTC | 7h 50m |
| 2026-05-21 | FDB461 | DXB → CCU | May 21, 21:25 UTC | May 22, 18:40 UTC | 21h 15m |
| 2026-05-21 | FDB564 | CGP → DXB | May 21, 03:45 UTC | May 21, 21:55 UTC | 18h 10m |
| 2026-05-20 | FDB563 | DXB → CGP | May 20, 23:10 UTC | May 21, 01:55 UTC | 2h 45m |
| 2026-05-19 | FDB524 | DAC → DXB | May 19, 16:15 UTC | May 19, 19:30 UTC | 3h 15m |
| 2026-05-19 | FDB523 | DXB → DAC | May 19, 11:45 UTC | May 19, 14:35 UTC | 2h 50m |
| 2026-05-18 | FDB523 | DXB → DAC | May 18, 16:15 UTC | May 19, 14:35 UTC | 22h 19m |
| 2026-05-18 | FDB1596 | KTM → DXB | May 18, 14:35 UTC | May 19, 12:30 UTC | 21h 54m |
| 2026-05-18 | FDB1595 | DXB → KTM | May 18, 11:00 UTC | May 18, 11:55 UTC | 55m |
| 2026-05-17 | FDB1596 | KTM → DXB | May 17, 15:40 UTC | May 18, 11:55 UTC | 20h 15m |
| 2026-05-17 | FDB1596 | KTM → DXB | May 17, 14:01 UTC | May 18, 11:55 UTC | 21h 55m |
| 2026-05-17 | FDB1595 | DXB → KTM | May 17, 11:15 UTC | May 17, 12:05 UTC | 50m |
| 2026-05-16 | FDB1596 | KTM → DXB | May 16, 15:50 UTC | May 17, 12:05 UTC | 20h 15m |
| 2026-05-16 | FDB1596 | KTM → DXB | May 16, 14:11 UTC | May 17, 12:05 UTC | 21h 55m |
| 2026-05-16 | FDB1595 | DXB → KTM | May 16, 11:11 UTC | May 16, 12:40 UTC | 1h 30m |
| 2026-05-15 | FDB75Y | MUX → DXB | May 15, 21:40 UTC | May 15, 21:45 UTC | 5m |
| 2026-05-15 | FDB1JC | DXB → MUX | May 15, 20:20 UTC | May 15, 20:30 UTC | 10m |
| 2026-05-14 | FDB1596 | KTM → DXB | May 14, 14:25 UTC | May 14, 17:15 UTC | 2h 50m |
| 2026-05-13 | FDB1595 | DXB → KTM | May 13, 21:20 UTC | May 14, 12:05 UTC | 14h 45m |
| 2026-05-13 | FDB569 | DXB → CMB | May 13, 17:40 UTC | May 13, 18:45 UTC | 1h 5m |
| 2026-05-13 | FDB569 | DXB → CMB | May 13, 14:55 UTC | May 13, 15:15 UTC | 20m |
| 2026-05-13 | FDB502 | DAC → DXB | May 13, 02:35 UTC | May 13, 05:55 UTC | 3h 20m |
| 2026-05-12 | FDB501 | DXB → DAC | May 12, 16:30 UTC | May 13, 00:50 UTC | 8h 20m |
| 2026-05-11 | FDB898 | MED → DXB | May 11, 11:20 UTC | May 11, 15:50 UTC | 4h 30m |
| 2026-05-10 | FDB391 | DXB → LYP | May 10, 04:09 UTC | May 10, 04:19 UTC | 10m |
| 2026-05-09 | FDB59J | BAH → DXB | May 9, 15:55 UTC | May 9, 16:45 UTC | 50m |
| 2026-05-09 | FDB5AY | DXB → BAH | May 9, 12:30 UTC | May 9, 13:20 UTC | 50m |
| 2026-05-08 | FDB1596 | KTM → DXB | May 8, 14:25 UTC | May 8, 15:45 UTC | 1h 20m |
| 2026-05-08 | FDB1595 | DXB → KTM | May 8, 12:14 UTC | May 8, 13:00 UTC | 45m |
| 2026-05-07 | FDB564 | CGP → DXB | May 7, 03:50 UTC | May 7, 04:55 UTC | 1h 5m |
| 2026-05-07 | FDB563 | DXB → CGP | May 7, 01:05 UTC | May 7, 02:05 UTC | 1h 0m |
| 2026-05-06 | FDB2HR | DXB → UET | May 6, 02:20 UTC | May 6, 02:40 UTC | 20m |
| 2026-05-05 | FDB647 | DXB → ADD | May 5, 12:40 UTC | May 5, 22:01 UTC | 9h 20m |
| 2026-05-05 | FDB74X | MUX → DXB | May 5, 08:35 UTC | May 5, 09:05 UTC | 30m |
| 2026-05-05 | FDB74X | MUX → DXB | May 5, 06:25 UTC | May 5, 06:30 UTC | 5m |
| 2026-05-05 | FDB9CE | DXB → MUX | May 5, 05:05 UTC | May 5, 05:15 UTC | 10m |
| 2026-05-04 | FDB524 | DAC → DXB | May 4, 16:25 UTC | May 4, 17:20 UTC | 55m |
| 2026-05-04 | FDB523 | DXB → DAC | May 4, 10:15 UTC | May 4, 14:25 UTC | 4h 10m |
| 2026-05-03 | FDB828 | MED → DXB | May 3, 18:05 UTC | May 4, 00:10 UTC | 6h 5m |
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-FQC page for operator, model, and routing details .