sensors Mode-S transponder
89668A
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPI · BOEING 737 MAX 8
- Hex
- 89668A
- Octal
- 42263212
- Decimal
- 9,004,682
- Country
- AE
- Tail
- A6-FPI
- Type
- B38M
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 89668A 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 |
|---|---|---|---|
| FDB1942 | Fly Dubai | 9 | 2026-05-27 |
| FDB1736 | Fly Dubai | 7 | 2026-05-28 |
| FDB1735 | Fly Dubai | 7 | 2026-04-26 |
| FDB1941 | Fly Dubai | 4 | 2026-04-25 |
| FDB14Q | - | 3 | 2026-04-13 |
| FDB873 | Fly Dubai | 2 | 2026-04-26 |
| FDB75L | Fly Dubai | 2 | 2026-04-18 |
| FDB749 | Fly Dubai | 2 | 2026-05-24 |
| FDB746 | Fly Dubai | 2 | 2026-05-22 |
| FDB539 | Fly Dubai | 2 | 2026-04-30 |
| FDB4TA | Fly Dubai | 2 | 2026-05-03 |
| FDB4MA | Fly Dubai | 2 | 2026-05-03 |
| FDB461 | Fly Dubai | 2 | 2026-04-22 |
| FDB3DK | Fly Dubai | 2 | 2026-05-23 |
| FDB15L | Fly Dubai | 2 | 2026-04-18 |
| FDB9UR | Fly Dubai | 1 | 2026-04-22 |
| FDB989 | Fly Dubai | 1 | 2026-04-28 |
| FDB864 | Fly Dubai | 1 | 2026-04-20 |
| FDB863 | Fly Dubai | 1 | 2026-04-20 |
| FDB833 | Fly Dubai | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB1736 | ALA → DXB | May 28, 02:35 UTC | May 29, 02:30 UTC | 23h 55m |
| 2026-05-27 | FDB1736 | ALA → DXB | May 27, 20:55 UTC | May 28, 02:40 UTC | 5h 45m |
| 2026-05-27 | FDB1942 | TAS → DXB | May 27, 01:34 UTC | May 27, 20:55 UTC | 19h 20m |
| 2026-05-26 | FDB5WB | BEY → DXB | May 26, 12:35 UTC | May 27, 01:39 UTC | 13h 5m |
| 2026-05-24 | FDB750 | TIV → DXB | May 24, 16:35 UTC | May 24, 21:15 UTC | 4h 40m |
| 2026-05-24 | FDB749 | DXB → TIV | May 24, 01:35 UTC | May 24, 14:20 UTC | 12h 45m |
| 2026-05-23 | FDB749 | DXB → TIV | May 23, 14:35 UTC | May 24, 14:20 UTC | 23h 45m |
| 2026-05-23 | FDB3DK | EBL → DXB | May 23, 14:15 UTC | May 24, 01:40 UTC | 11h 26m |
| 2026-05-23 | FDB3DK | EBL → DXB | May 23, 02:50 UTC | May 24, 01:40 UTC | 22h 51m |
| 2026-05-22 | FDB746 | TIA → DXB | May 22, 15:05 UTC | May 23, 14:30 UTC | 23h 24m |
| 2026-05-22 | FDB746 | TIA → DXB | May 22, 11:20 UTC | May 23, 02:55 UTC | 15h 35m |
| 2026-05-21 | FDB34Q | DXB → TIA | May 21, 15:50 UTC | May 22, 09:15 UTC | 17h 25m |
| 2026-05-20 | FDB2MF | IST → DXB | May 20, 16:55 UTC | May 20, 20:45 UTC | 3h 50m |
| 2026-05-20 | FDB4GP | DXB → IST | May 20, 15:05 UTC | May 20, 15:15 UTC | 10m |
| 2026-05-19 | FDB7UE | EVN → DXB | May 19, 11:25 UTC | May 20, 03:40 UTC | 16h 15m |
| 2026-05-19 | FDB59G | DXB → EVN | May 19, 03:55 UTC | May 19, 06:50 UTC | 2h 55m |
| 2026-05-13 | FDB1721 | DXB → ALA | May 13, 17:15 UTC | May 13, 17:35 UTC | 20m |
| 2026-05-12 | FDB1736 | ALA → DXB | May 12, 20:40 UTC | May 13, 02:20 UTC | 5h 40m |
| 2026-05-10 | FDB1NB | VKO → DXB | May 10, 03:25 UTC | May 11, 01:55 UTC | 22h 30m |
| 2026-05-08 | FDB1304 | NQZ → DXB | May 8, 02:35 UTC | May 9, 01:10 UTC | 22h 35m |
| 2026-05-05 | FDB1942 | TAS → DXB | May 5, 01:30 UTC | May 5, 19:30 UTC | 18h 0m |
| 2026-05-04 | FDB1942 | TAS → DXB | May 4, 20:25 UTC | May 5, 01:30 UTC | 5h 5m |
| 2026-05-04 | FDB5GE | OTP → DXB | May 4, 06:45 UTC | May 4, 11:50 UTC | 5h 5m |
| 2026-05-03 | FDB1NU | DXB → OTP | May 3, 22:30 UTC | May 4, 03:30 UTC | 5h 0m |
| 2026-05-03 | FDB4TA | ZAG → DXB | May 3, 13:00 UTC | May 3, 18:50 UTC | 5h 50m |
| 2026-05-03 | FDB4MA | DXB → ZAG | May 3, 06:00 UTC | May 3, 11:20 UTC | 5h 20m |
| 2026-04-30 | FDB540 | KTM → DXB | Apr 30, 11:30 UTC | Apr 30, 15:45 UTC | 4h 15m |
| 2026-04-30 | FDB539 | DXB → KTM | Apr 30, 07:25 UTC | Apr 30, 09:10 UTC | 1h 45m |
| 2026-04-30 | FDB539 | DXB → KTM | Apr 30, 05:15 UTC | Apr 30, 05:40 UTC | 25m |
| 2026-04-29 | FDB4TA | ZAG → DXB | Apr 29, 12:55 UTC | Apr 29, 18:25 UTC | 5h 30m |
| 2026-04-29 | FDB4MA | DXB → ZAG | Apr 29, 04:20 UTC | Apr 29, 10:50 UTC | 6h 31m |
| 2026-04-28 | FDB5YA | VKO → DXB | Apr 28, 20:15 UTC | Apr 28, 22:40 UTC | 2h 25m |
| 2026-04-28 | FDB989 | DXB → VKO | Apr 28, 04:55 UTC | Apr 28, 05:15 UTC | 20m |
| 2026-04-27 | FDB1736 | ALA → DXB | Apr 27, 06:05 UTC | Apr 27, 06:25 UTC | 20m |
| 2026-04-26 | FDB1735 | DXB → ALA | Apr 26, 18:20 UTC | Apr 26, 18:45 UTC | 25m |
| 2026-04-26 | FDB873 | DXB → TIF | Apr 26, 07:25 UTC | Apr 26, 13:45 UTC | 6h 20m |
| 2026-04-26 | FDB1942 | TAS → DXB | Apr 26, 02:55 UTC | Apr 26, 03:15 UTC | 20m |
| 2026-04-25 | FDB1941 | DXB → TAS | Apr 25, 17:40 UTC | Apr 25, 18:00 UTC | 20m |
| 2026-04-25 | FDB1690 | FRU → DXB | Apr 25, 03:55 UTC | Apr 25, 04:15 UTC | 20m |
| 2026-04-24 | FDB833 | DXB → JED | Apr 24, 07:40 UTC | Apr 24, 14:10 UTC | 6h 30m |
| 2026-04-24 | FDB1942 | TAS → DXB | Apr 24, 03:00 UTC | Apr 24, 03:20 UTC | 20m |
| 2026-04-23 | FDB873 | DXB → TIF | Apr 23, 07:05 UTC | Apr 23, 13:15 UTC | 6h 10m |
| 2026-04-22 | FDB9UR | CCU → DXB | Apr 22, 21:00 UTC | Apr 23, 01:35 UTC | 4h 35m |
| 2026-04-22 | FDB461 | DXB → CCU | Apr 22, 18:20 UTC | Apr 22, 19:15 UTC | 55m |
| 2026-04-22 | FDB461 | DXB → CCU | Apr 22, 15:05 UTC | Apr 22, 15:25 UTC | 20m |
| 2026-04-22 | FDB1736 | ALA → DXB | Apr 22, 04:15 UTC | Apr 22, 04:35 UTC | 20m |
| 2026-04-21 | FDB1735 | DXB → ALA | Apr 21, 18:10 UTC | Apr 21, 18:30 UTC | 20m |
| 2026-04-21 | FDB1134 | KTM → DXB | Apr 21, 04:15 UTC | Apr 21, 07:50 UTC | 3h 35m |
| 2026-04-20 | FDB1133 | DXB → KTM | Apr 20, 22:10 UTC | Apr 21, 02:15 UTC | 4h 5m |
| 2026-04-20 | FDB864 | DMM → DXB | Apr 20, 12:45 UTC | Apr 20, 14:15 UTC | 1h 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-FPI page for operator, model, and routing details .