sensors Mode-S transponder
896643
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FQE · BOEING 737 MAX 8
- Hex
- 896643
- Octal
- 42263103
- Decimal
- 9,004,611
- Country
- AE
- Tail
- A6-FQE
- Type
- B38M
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 896643 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 |
|---|---|---|---|
| FDB564 | Fly Dubai | 10 | 2026-05-27 |
| FDB563 | Fly Dubai | 9 | 2026-05-16 |
| FDB1595 | Fly Dubai | 8 | 2026-05-27 |
| FDB1596 | Fly Dubai | 7 | 2026-05-28 |
| FDB392 | Fly Dubai | 6 | 2026-04-29 |
| FDB524 | Fly Dubai | 5 | 2026-05-18 |
| FDB523 | Fly Dubai | 5 | 2026-05-18 |
| FDB391 | Fly Dubai | 5 | 2026-04-29 |
| FDB909 | Fly Dubai | 4 | 2026-05-14 |
| FDB574 | Fly Dubai | 4 | 2026-05-29 |
| FDB502 | Fly Dubai | 4 | 2026-05-24 |
| FDB501 | Fly Dubai | 4 | 2026-05-23 |
| FDB832 | Fly Dubai | 3 | 2026-05-08 |
| FDB827 | Fly Dubai | 3 | 2026-04-29 |
| FDB808 | Fly Dubai | 3 | 2026-05-19 |
| FDB573 | Fly Dubai | 3 | 2026-05-29 |
| FDB570 | Fly Dubai | 3 | 2026-05-14 |
| FDB4DT | Fly Dubai | 3 | 2026-04-27 |
| FDB9UR | Fly Dubai | 2 | 2026-05-13 |
| FDB9CE | Fly Dubai | 2 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB574 | KTM → DXB | May 29, 18:00 UTC | May 29, 19:35 UTC | 1h 35m |
| 2026-05-29 | FDB573 | DXB → KTM | May 29, 06:25 UTC | May 29, 15:45 UTC | 9h 20m |
| 2026-05-28 | FDB1596 | KTM → DXB | May 28, 14:20 UTC | May 29, 04:30 UTC | 14h 10m |
| 2026-05-27 | FDB1595 | DXB → KTM | May 27, 21:55 UTC | May 28, 12:50 UTC | 14h 55m |
| 2026-05-27 | FDB1595 | DXB → KTM | May 27, 17:45 UTC | May 28, 12:50 UTC | 19h 5m |
| 2026-05-27 | FDB1595 | DXB → KTM | May 27, 16:00 UTC | May 28, 12:50 UTC | 20h 50m |
| 2026-05-27 | FDB564 | CGP → DXB | May 27, 06:15 UTC | May 27, 22:55 UTC | 16h 41m |
| 2026-05-27 | FDB564 | CGP → DXB | May 27, 04:04 UTC | May 27, 22:55 UTC | 18h 51m |
| 2026-05-26 | FDB1596 | KTM → DXB | May 26, 14:40 UTC | May 27, 00:00 UTC | 9h 20m |
| 2026-05-26 | FDB1595 | DXB → KTM | May 26, 11:20 UTC | May 26, 13:10 UTC | 1h 50m |
| 2026-05-25 | FDB1595 | DXB → KTM | May 25, 13:05 UTC | May 26, 12:45 UTC | 23h 39m |
| 2026-05-24 | FDB1596 | KTM → DXB | May 24, 14:50 UTC | May 25, 13:45 UTC | 22h 55m |
| 2026-05-24 | FDB1596 | KTM → DXB | May 24, 14:30 UTC | May 24, 16:20 UTC | 1h 50m |
| 2026-05-24 | FDB502 | DAC → DXB | May 24, 02:55 UTC | May 24, 13:05 UTC | 10h 10m |
| 2026-05-23 | FDB501 | DXB → DAC | May 23, 22:15 UTC | May 24, 01:10 UTC | 2h 55m |
| 2026-05-23 | FDB501 | DXB → DAC | May 23, 06:30 UTC | May 24, 01:10 UTC | 18h 40m |
| 2026-05-22 | FDB8850 | RUH → DXB | May 22, 15:45 UTC | May 22, 17:50 UTC | 2h 5m |
| 2026-05-22 | FDB8849 | DXB → RUH | May 22, 11:40 UTC | May 22, 13:35 UTC | 1h 55m |
| 2026-05-20 | FDB74X | MUX → DXB | May 20, 06:20 UTC | May 20, 06:25 UTC | 5m |
| 2026-05-20 | FDB9CE | DXB → MUX | May 20, 04:50 UTC | May 20, 05:05 UTC | 15m |
| 2026-05-19 | FDB808 | JED → DXB | May 19, 06:25 UTC | May 19, 22:05 UTC | 15h 40m |
| 2026-05-18 | FDB524 | DAC → DXB | May 18, 16:15 UTC | May 19, 04:20 UTC | 12h 4m |
| 2026-05-18 | FDB523 | DXB → DAC | May 18, 11:45 UTC | May 18, 14:40 UTC | 2h 55m |
| 2026-05-17 | FDB564 | CGP → DXB | May 17, 03:50 UTC | May 17, 07:00 UTC | 3h 10m |
| 2026-05-16 | FDB563 | DXB → CGP | May 16, 16:00 UTC | May 17, 02:00 UTC | 10h 0m |
| 2026-05-15 | FDB910 | JED → DXB | May 15, 11:00 UTC | May 15, 11:35 UTC | 35m |
| 2026-05-14 | FDB570 | CMB → DXB | May 14, 21:10 UTC | May 14, 21:55 UTC | 45m |
| 2026-05-14 | FDB909 | DXB → JED | May 14, 05:40 UTC | May 14, 18:45 UTC | 13h 5m |
| 2026-05-13 | FDB9UR | CCU → DXB | May 13, 20:20 UTC | May 13, 23:20 UTC | 3h 0m |
| 2026-05-13 | FDB564 | CGP → DXB | May 13, 03:35 UTC | May 13, 18:35 UTC | 15h 0m |
| 2026-05-12 | FDB1596 | KTM → DXB | May 12, 14:30 UTC | May 13, 02:00 UTC | 11h 30m |
| 2026-05-12 | FDB1595 | DXB → KTM | May 12, 11:15 UTC | May 12, 12:15 UTC | 1h 0m |
| 2026-05-11 | FDB564 | CGP → DXB | May 11, 03:55 UTC | May 11, 21:35 UTC | 17h 40m |
| 2026-05-10 | FDB563 | DXB → CGP | May 10, 11:05 UTC | May 11, 02:00 UTC | 14h 55m |
| 2026-05-08 | FDB832 | JED → DXB | May 8, 12:04 UTC | May 9, 06:40 UTC | 18h 35m |
| 2026-05-08 | FDB502 | DAC → DXB | May 8, 02:19 UTC | May 8, 18:15 UTC | 15h 55m |
| 2026-05-07 | FDB501 | DXB → DAC | May 7, 23:49 UTC | May 8, 00:49 UTC | 1h 0m |
| 2026-05-06 | FDB9UR | CCU → DXB | May 6, 20:10 UTC | May 6, 20:50 UTC | 40m |
| 2026-05-06 | FDB564 | CGP → DXB | May 6, 03:45 UTC | May 6, 18:40 UTC | 14h 54m |
| 2026-05-06 | FDB563 | DXB → CGP | May 6, 01:01 UTC | May 6, 01:55 UTC | 55m |
| 2026-05-05 | FDB910 | JED → DXB | May 5, 06:50 UTC | May 5, 13:15 UTC | 6h 25m |
| 2026-05-04 | FDB570 | CMB → DXB | May 4, 21:15 UTC | May 4, 22:55 UTC | 1h 40m |
| 2026-05-04 | FDB569 | DXB → CMB | May 4, 15:05 UTC | May 4, 18:55 UTC | 3h 51m |
| 2026-05-04 | FDB346 | UET → DXB | May 4, 07:40 UTC | May 4, 08:00 UTC | 20m |
| 2026-05-04 | FDB2HR | DXB → UET | May 4, 02:25 UTC | May 4, 02:50 UTC | 25m |
| 2026-05-03 | FDB540 | KTM → DXB | May 3, 15:50 UTC | May 3, 16:09 UTC | 20m |
| 2026-05-03 | FDB540 | KTM → DXB | May 3, 11:55 UTC | May 3, 13:40 UTC | 1h 45m |
| 2026-05-02 | FDB524 | DAC → DXB | May 2, 16:20 UTC | May 3, 07:55 UTC | 15h 34m |
| 2026-05-02 | FDB523 | DXB → DAC | May 2, 10:05 UTC | May 2, 14:25 UTC | 4h 20m |
| 2026-05-02 | FDB832 | JED → DXB | May 2, 01:00 UTC | May 2, 07:40 UTC | 6h 40m |
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-FQE page for operator, model, and routing details .