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