sensors Mode-S transponder
89660B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FQA · BOEING 737 MAX 8
- Hex
- 89660B
- Octal
- 42263013
- Decimal
- 9,004,555
- Country
- AE
- Tail
- A6-FQA
- Type
- B38M
- Flights observed
- 92
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address 89660B 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 |
|---|---|---|---|
| FDB573 | Fly Dubai | 7 | 2026-04-26 |
| FDB574 | Fly Dubai | 6 | 2026-04-26 |
| FDB564 | Fly Dubai | 6 | 2026-05-05 |
| FDB570 | Fly Dubai | 5 | 2026-05-02 |
| FDB563 | Fly Dubai | 5 | 2026-05-05 |
| FDB1595 | Fly Dubai | 5 | 2026-05-09 |
| FDB391 | Fly Dubai | 4 | 2026-05-04 |
| FDB9FX | Fly Dubai | 3 | 2026-04-29 |
| FDB9CE | Fly Dubai | 3 | 2026-05-01 |
| FDB74X | Fly Dubai | 3 | 2026-05-01 |
| FDB569 | Fly Dubai | 3 | 2026-05-01 |
| FDB392 | Fly Dubai | 3 | 2026-05-04 |
| FDB2HR | Fly Dubai | 3 | 2026-04-24 |
| FDB1596 | Fly Dubai | 3 | 2026-05-09 |
| FDB910 | Fly Dubai | 2 | 2026-05-08 |
| FDB909 | Fly Dubai | 2 | 2026-04-28 |
| FDB897 | Fly Dubai | 2 | 2026-04-16 |
| FDB808 | Fly Dubai | 2 | 2026-04-21 |
| FDB807 | - | 2 | 2026-04-13 |
| FDB648 | Fly Dubai | 2 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-09 | FDB1596 | KTM → DXB | May 9, 15:25 UTC | May 9, 17:49 UTC | 2h 25m |
| 2026-05-09 | FDB1595 | DXB → KTM | May 9, 11:50 UTC | May 9, 13:20 UTC | 1h 30m |
| 2026-05-08 | FDB1JC | DXB → MUX | May 8, 21:05 UTC | May 8, 21:15 UTC | 10m |
| 2026-05-08 | FDB910 | JED → DXB | May 8, 11:09 UTC | May 8, 11:44 UTC | 35m |
| 2026-05-07 | FDB910 | JED → DXB | May 7, 15:10 UTC | May 8, 11:44 UTC | 20h 35m |
| 2026-05-07 | FDB1595 | DXB → KTM | May 7, 11:20 UTC | May 7, 12:45 UTC | 1h 25m |
| 2026-05-06 | FDB75Y | MUX → DXB | May 6, 21:50 UTC | May 6, 21:55 UTC | 5m |
| 2026-05-06 | FDB1JC | DXB → MUX | May 6, 20:30 UTC | May 6, 20:40 UTC | 10m |
| 2026-05-06 | FDB540 | KTM → DXB | May 6, 10:35 UTC | May 6, 11:20 UTC | 45m |
| 2026-05-06 | FDB539 | DXB → KTM | May 6, 08:01 UTC | May 6, 08:15 UTC | 15m |
| 2026-05-05 | FDB564 | CGP → DXB | May 5, 08:40 UTC | May 5, 09:00 UTC | 20m |
| 2026-05-05 | FDB564 | CGP → DXB | May 5, 04:00 UTC | May 5, 05:00 UTC | 1h 0m |
| 2026-05-05 | FDB563 | DXB → CGP | May 5, 01:00 UTC | May 5, 01:55 UTC | 55m |
| 2026-05-04 | FDB392 | LYP → DXB | May 4, 06:20 UTC | May 4, 09:00 UTC | 2h 40m |
| 2026-05-04 | FDB391 | DXB → LYP | May 4, 02:15 UTC | May 4, 02:39 UTC | 25m |
| 2026-05-03 | FDB1596 | KTM → DXB | May 3, 14:45 UTC | May 3, 19:05 UTC | 4h 20m |
| 2026-05-03 | FDB1595 | DXB → KTM | May 3, 09:20 UTC | May 3, 12:20 UTC | 3h 0m |
| 2026-05-02 | FDB1596 | KTM → DXB | May 2, 14:35 UTC | May 3, 06:10 UTC | 15h 34m |
| 2026-05-02 | FDB1595 | DXB → KTM | May 2, 11:15 UTC | May 2, 12:40 UTC | 1h 25m |
| 2026-05-02 | FDB1595 | DXB → KTM | May 2, 09:10 UTC | May 2, 09:30 UTC | 20m |
| 2026-05-02 | FDB570 | CMB → DXB | May 2, 00:30 UTC | May 2, 00:50 UTC | 20m |
| 2026-05-01 | FDB570 | CMB → DXB | May 1, 21:05 UTC | May 1, 22:50 UTC | 1h 45m |
| 2026-05-01 | FDB569 | DXB → CMB | May 1, 14:55 UTC | May 1, 18:40 UTC | 3h 45m |
| 2026-05-01 | FDB74X | MUX → DXB | May 1, 08:20 UTC | May 1, 08:45 UTC | 25m |
| 2026-05-01 | FDB74X | MUX → DXB | May 1, 06:15 UTC | May 1, 06:20 UTC | 5m |
| 2026-05-01 | FDB9CE | DXB → MUX | May 1, 04:55 UTC | May 1, 05:05 UTC | 10m |
| 2026-05-01 | FDB9CE | DXB → MUX | May 1, 02:50 UTC | May 1, 03:15 UTC | 25m |
| 2026-04-30 | FDB648 | ADD → DXB | Apr 30, 12:15 UTC | Apr 30, 22:00 UTC | 9h 45m |
| 2026-04-30 | FDB832 | JED → DXB | Apr 30, 00:45 UTC | Apr 30, 07:25 UTC | 6h 40m |
| 2026-04-29 | FDB648 | ADD → DXB | Apr 29, 12:05 UTC | Apr 29, 21:15 UTC | 9h 10m |
| 2026-04-29 | FDB9FX | SKT → DXB | Apr 29, 03:19 UTC | Apr 29, 03:55 UTC | 35m |
| 2026-04-28 | FDB9FX | SKT → DXB | Apr 28, 22:35 UTC | Apr 29, 01:20 UTC | 2h 45m |
| 2026-04-28 | FDB4DT | DXB → SKT | Apr 28, 20:30 UTC | Apr 28, 20:55 UTC | 25m |
| 2026-04-28 | FDB909 | DXB → JED | Apr 28, 06:25 UTC | Apr 28, 13:10 UTC | 6h 45m |
| 2026-04-27 | FDB392 | LYP → DXB | Apr 27, 06:35 UTC | Apr 27, 09:15 UTC | 2h 40m |
| 2026-04-27 | FDB391 | DXB → LYP | Apr 27, 02:00 UTC | Apr 27, 02:25 UTC | 25m |
| 2026-04-26 | FDB574 | KTM → DXB | Apr 26, 17:35 UTC | Apr 26, 21:55 UTC | 4h 20m |
| 2026-04-26 | FDB573 | DXB → KTM | Apr 26, 12:05 UTC | Apr 26, 15:55 UTC | 3h 50m |
| 2026-04-26 | FDB564 | CGP → DXB | Apr 26, 08:25 UTC | Apr 26, 08:45 UTC | 20m |
| 2026-04-26 | FDB564 | CGP → DXB | Apr 26, 03:55 UTC | Apr 26, 04:55 UTC | 1h 0m |
| 2026-04-26 | FDB563 | DXB → CGP | Apr 26, 01:15 UTC | Apr 26, 02:10 UTC | 55m |
| 2026-04-25 | FDB563 | DXB → CGP | Apr 25, 21:45 UTC | Apr 25, 22:10 UTC | 25m |
| 2026-04-25 | FDB392 | LYP → DXB | Apr 25, 08:30 UTC | Apr 25, 08:55 UTC | 25m |
| 2026-04-25 | FDB391 | DXB → LYP | Apr 25, 01:55 UTC | Apr 25, 02:25 UTC | 30m |
| 2026-04-24 | FDB574 | KTM → DXB | Apr 24, 18:40 UTC | Apr 24, 22:45 UTC | 4h 5m |
| 2026-04-24 | FDB573 | DXB → KTM | Apr 24, 14:25 UTC | Apr 24, 16:05 UTC | 1h 40m |
| 2026-04-24 | FDB573 | DXB → KTM | Apr 24, 12:10 UTC | Apr 24, 12:30 UTC | 20m |
| 2026-04-24 | FDB346 | UET → DXB | Apr 24, 07:35 UTC | Apr 24, 07:55 UTC | 20m |
| 2026-04-24 | FDB2HR | DXB → UET | Apr 24, 02:20 UTC | Apr 24, 02:40 UTC | 20m |
| 2026-04-23 | FDB8068 | - | Apr 23, 14:05 UTC | Apr 23, 14:35 UTC | 30m |
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-FQA page for operator, model, and routing details .