sensors Mode-S transponder
89666D
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FQL · BOEING 737 MAX 8
- Hex
- 89666D
- Octal
- 42263155
- Decimal
- 9,004,653
- Country
- AE
- Tail
- A6-FQL
- Type
- B38M
- Flights observed
- 105
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 89666D 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 |
|---|---|---|---|
| FDB524 | Fly Dubai | 8 | 2026-05-26 |
| FDB570 | Fly Dubai | 7 | 2026-05-17 |
| FDB569 | Fly Dubai | 6 | 2026-05-17 |
| FDB523 | Fly Dubai | 6 | 2026-05-20 |
| FDB897 | Fly Dubai | 5 | 2026-04-30 |
| FDB392 | Fly Dubai | 5 | 2026-05-24 |
| FDB1595 | Fly Dubai | 4 | 2026-05-10 |
| FDB9CE | Fly Dubai | 3 | 2026-05-25 |
| FDB898 | Fly Dubai | 3 | 2026-05-16 |
| FDB828 | Fly Dubai | 3 | 2026-05-27 |
| FDB74X | Fly Dubai | 3 | 2026-05-25 |
| FDB642 | Fly Dubai | 3 | 2026-04-29 |
| FDB564 | Fly Dubai | 3 | 2026-05-10 |
| FDB563 | Fly Dubai | 3 | 2026-05-09 |
| FDB391 | Fly Dubai | 3 | 2026-05-06 |
| FDB1596 | Fly Dubai | 3 | 2026-05-11 |
| FDB9ST | Fly Dubai | 2 | 2026-04-22 |
| FDB9FX | Fly Dubai | 2 | 2026-04-25 |
| FDB827 | Fly Dubai | 2 | 2026-04-14 |
| FDB75Y | Fly Dubai | 2 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB832 | JED → DXB | May 28, 17:10 UTC | May 29, 06:30 UTC | 13h 20m |
| 2026-05-27 | FDB876 | TIF → DXB | May 27, 23:20 UTC | May 28, 17:45 UTC | 18h 25m |
| 2026-05-27 | FDB828 | MED → DXB | May 27, 23:05 UTC | May 28, 17:45 UTC | 18h 40m |
| 2026-05-27 | FDB828 | MED → DXB | May 27, 06:04 UTC | May 27, 23:40 UTC | 17h 35m |
| 2026-05-26 | FDB524 | DAC → DXB | May 26, 16:15 UTC | May 26, 19:34 UTC | 3h 20m |
| 2026-05-26 | FDB502 | DAC → DXB | May 26, 02:24 UTC | May 26, 14:55 UTC | 12h 30m |
| 2026-05-25 | FDB501 | DXB → DAC | May 25, 22:19 UTC | May 26, 01:10 UTC | 2h 50m |
| 2026-05-25 | FDB74X | MUX → DXB | May 25, 06:15 UTC | May 25, 06:20 UTC | 5m |
| 2026-05-25 | FDB9CE | DXB → MUX | May 25, 05:00 UTC | May 25, 05:10 UTC | 10m |
| 2026-05-24 | FDB392 | LYP → DXB | May 24, 06:25 UTC | May 24, 06:35 UTC | 10m |
| 2026-05-22 | FDB392 | LYP → DXB | May 22, 06:30 UTC | May 22, 06:45 UTC | 15m |
| 2026-05-20 | FDB524 | DAC → DXB | May 20, 16:05 UTC | May 20, 19:20 UTC | 3h 15m |
| 2026-05-20 | FDB523 | DXB → DAC | May 20, 11:45 UTC | May 20, 14:35 UTC | 2h 50m |
| 2026-05-19 | FDB540 | KTM → DXB | May 19, 09:50 UTC | May 19, 12:30 UTC | 2h 40m |
| 2026-05-18 | FDB539 | DXB → KTM | May 18, 15:30 UTC | May 19, 08:00 UTC | 16h 29m |
| 2026-05-18 | FDB539 | DXB → KTM | May 18, 11:30 UTC | May 19, 08:00 UTC | 20h 29m |
| 2026-05-17 | FDB570 | CMB → DXB | May 17, 21:20 UTC | May 18, 16:10 UTC | 18h 50m |
| 2026-05-17 | FDB570 | CMB → DXB | May 17, 21:10 UTC | May 18, 16:10 UTC | 19h 0m |
| 2026-05-17 | FDB569 | DXB → CMB | May 17, 16:50 UTC | May 17, 18:45 UTC | 1h 55m |
| 2026-05-17 | FDB9CE | DXB → MUX | May 17, 04:40 UTC | May 17, 05:05 UTC | 25m |
| 2026-05-16 | FDB898 | MED → DXB | May 16, 15:25 UTC | May 16, 16:00 UTC | 35m |
| 2026-05-15 | FDB898 | MED → DXB | May 15, 19:20 UTC | May 16, 16:00 UTC | 20h 41m |
| 2026-05-15 | FDB524 | DAC → DXB | May 15, 17:20 UTC | May 16, 16:00 UTC | 22h 41m |
| 2026-05-15 | FDB524 | DAC → DXB | May 15, 16:10 UTC | May 15, 19:30 UTC | 3h 20m |
| 2026-05-15 | FDB523 | DXB → DAC | May 15, 06:05 UTC | May 15, 14:30 UTC | 8h 25m |
| 2026-05-14 | FDB524 | DAC → DXB | May 14, 21:00 UTC | May 14, 21:15 UTC | 15m |
| 2026-05-14 | FDB524 | DAC → DXB | May 14, 16:15 UTC | May 14, 19:30 UTC | 3h 15m |
| 2026-05-14 | FDB502 | DAC → DXB | May 14, 02:15 UTC | May 14, 14:30 UTC | 12h 15m |
| 2026-05-13 | FDB501 | DXB → DAC | May 13, 06:45 UTC | May 14, 00:50 UTC | 18h 5m |
| 2026-05-11 | FDB1596 | KTM → DXB | May 11, 14:30 UTC | May 11, 17:10 UTC | 2h 41m |
| 2026-05-10 | FDB1595 | DXB → KTM | May 10, 21:10 UTC | May 11, 12:40 UTC | 15h 30m |
| 2026-05-10 | FDB1595 | DXB → KTM | May 10, 16:44 UTC | May 11, 12:40 UTC | 19h 55m |
| 2026-05-10 | FDB564 | CGP → DXB | May 10, 04:00 UTC | May 10, 21:44 UTC | 17h 45m |
| 2026-05-09 | FDB563 | DXB → CGP | May 9, 10:50 UTC | May 10, 02:14 UTC | 15h 25m |
| 2026-05-08 | FDB570 | CMB → DXB | May 8, 21:30 UTC | May 9, 15:35 UTC | 18h 5m |
| 2026-05-08 | FDB569 | DXB → CMB | May 8, 17:30 UTC | May 9, 15:35 UTC | 22h 5m |
| 2026-05-08 | FDB564 | CGP → DXB | May 8, 03:49 UTC | May 8, 22:15 UTC | 18h 25m |
| 2026-05-07 | FDB563 | DXB → CGP | May 7, 13:10 UTC | May 8, 02:04 UTC | 12h 54m |
| 2026-05-06 | FDB570 | CMB → DXB | May 6, 21:25 UTC | May 7, 01:05 UTC | 3h 40m |
| 2026-05-06 | FDB569 | DXB → CMB | May 6, 04:25 UTC | May 6, 18:55 UTC | 14h 29m |
| 2026-05-06 | FDB391 | DXB → LYP | May 6, 02:05 UTC | May 6, 02:30 UTC | 25m |
| 2026-05-04 | FDB881 | DXB → TUU | May 4, 11:00 UTC | May 4, 17:40 UTC | 6h 40m |
| 2026-05-03 | FDB524 | DAC → DXB | May 3, 15:55 UTC | May 3, 21:05 UTC | 5h 10m |
| 2026-05-03 | FDB523 | DXB → DAC | May 3, 13:30 UTC | May 3, 14:25 UTC | 55m |
| 2026-05-03 | FDB523 | DXB → DAC | May 3, 10:20 UTC | May 3, 10:35 UTC | 15m |
| 2026-05-02 | FDB570 | CMB → DXB | May 2, 21:20 UTC | May 2, 23:00 UTC | 1h 40m |
| 2026-05-02 | FDB569 | DXB → CMB | May 2, 15:35 UTC | May 2, 19:20 UTC | 3h 45m |
| 2026-05-02 | FDB392 | LYP → DXB | May 2, 08:45 UTC | May 2, 09:05 UTC | 20m |
| 2026-05-02 | FDB392 | LYP → DXB | May 2, 06:30 UTC | May 2, 06:40 UTC | 10m |
| 2026-05-02 | FDB391 | DXB → LYP | May 2, 02:05 UTC | May 2, 02:30 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-FQL page for operator, model, and routing details .