sensors Mode-S transponder
896662
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FQI · BOEING 737 MAX 8
- Hex
- 896662
- Octal
- 42263142
- Decimal
- 9,004,642
- Country
- AE
- Tail
- A6-FQI
- Type
- B38M
- Flights observed
- 114
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 896662 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 |
|---|---|---|---|
| FDB523 | Fly Dubai | 11 | 2026-05-15 |
| FDB524 | Fly Dubai | 9 | 2026-05-16 |
| FDB9CE | Fly Dubai | 8 | 2026-05-19 |
| FDB574 | Fly Dubai | 6 | 2026-05-23 |
| FDB74X | Fly Dubai | 5 | 2026-05-14 |
| FDB573 | Fly Dubai | 5 | 2026-05-09 |
| FDB570 | Fly Dubai | 5 | 2026-05-25 |
| FDB569 | Fly Dubai | 5 | 2026-05-25 |
| FDB1JC | Fly Dubai | 5 | 2026-05-13 |
| FDB1596 | Fly Dubai | 5 | 2026-05-27 |
| FDB881 | Fly Dubai | 4 | 2026-05-02 |
| FDB1595 | Fly Dubai | 4 | 2026-05-27 |
| FDB897 | Fly Dubai | 3 | 2026-04-26 |
| FDB75Y | Fly Dubai | 3 | 2026-05-04 |
| FDB502 | Fly Dubai | 3 | 2026-05-29 |
| FDB501 | Fly Dubai | 3 | 2026-05-28 |
| FDB392 | Fly Dubai | 3 | 2026-04-17 |
| FDB9UR | Fly Dubai | 2 | 2026-05-15 |
| FDB830 | Fly Dubai | 2 | 2026-05-26 |
| FDB641 | Fly Dubai | 2 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB502 | DAC → DXB | May 29, 02:20 UTC | May 29, 17:30 UTC | 15h 10m |
| 2026-05-28 | FDB501 | DXB → DAC | May 28, 15:25 UTC | May 29, 00:50 UTC | 9h 25m |
| 2026-05-27 | FDB1596 | KTM → DXB | May 27, 16:35 UTC | May 28, 15:50 UTC | 23h 15m |
| 2026-05-27 | FDB1596 | KTM → DXB | May 27, 14:30 UTC | May 27, 17:10 UTC | 2h 40m |
| 2026-05-27 | FDB1595 | DXB → KTM | May 27, 11:20 UTC | May 27, 13:10 UTC | 1h 50m |
| 2026-05-26 | FDB830 | JED → DXB | May 26, 16:15 UTC | May 27, 06:55 UTC | 14h 40m |
| 2026-05-25 | FDB830 | JED → DXB | May 25, 22:34 UTC | May 26, 16:45 UTC | 18h 10m |
| 2026-05-25 | FDB570 | CMB → DXB | May 25, 20:59 UTC | May 26, 16:45 UTC | 19h 45m |
| 2026-05-25 | FDB569 | DXB → CMB | May 25, 07:35 UTC | May 25, 19:00 UTC | 11h 25m |
| 2026-05-24 | FDB569 | DXB → CMB | May 24, 21:10 UTC | May 25, 19:00 UTC | 21h 50m |
| 2026-05-23 | FDB574 | KTM → DXB | May 23, 18:35 UTC | May 23, 21:15 UTC | 2h 40m |
| 2026-05-23 | FDB564 | CGP → DXB | May 23, 04:15 UTC | May 23, 17:15 UTC | 13h 0m |
| 2026-05-22 | FDB1596 | KTM → DXB | May 22, 14:25 UTC | May 23, 02:05 UTC | 11h 40m |
| 2026-05-21 | FDB1595 | DXB → KTM | May 21, 23:15 UTC | May 22, 12:40 UTC | 13h 25m |
| 2026-05-21 | FDB437 | DXB → AMD | May 21, 06:20 UTC | May 21, 21:55 UTC | 15h 35m |
| 2026-05-20 | FDB1596 | KTM → DXB | May 20, 14:25 UTC | May 20, 16:55 UTC | 2h 30m |
| 2026-05-20 | FDB1595 | DXB → KTM | May 20, 11:15 UTC | May 20, 12:10 UTC | 55m |
| 2026-05-19 | FDB9CE | DXB → MUX | May 19, 04:45 UTC | May 19, 05:00 UTC | 15m |
| 2026-05-18 | FDB910 | JED → DXB | May 18, 11:00 UTC | May 18, 11:30 UTC | 30m |
| 2026-05-16 | FDB524 | DAC → DXB | May 16, 16:15 UTC | May 16, 19:30 UTC | 3h 15m |
| 2026-05-15 | FDB523 | DXB → DAC | May 15, 20:35 UTC | May 16, 14:35 UTC | 18h 1m |
| 2026-05-15 | FDB9UR | CCU → DXB | May 15, 20:25 UTC | May 16, 14:35 UTC | 18h 11m |
| 2026-05-15 | FDB564 | CGP → DXB | May 15, 03:55 UTC | May 15, 18:45 UTC | 14h 49m |
| 2026-05-14 | FDB563 | DXB → CGP | May 14, 23:25 UTC | May 15, 02:10 UTC | 2h 45m |
| 2026-05-14 | FDB563 | DXB → CGP | May 14, 21:55 UTC | May 14, 22:15 UTC | 20m |
| 2026-05-14 | FDB74X | MUX → DXB | May 14, 07:05 UTC | May 14, 07:10 UTC | 5m |
| 2026-05-14 | FDB9CE | DXB → MUX | May 14, 05:35 UTC | May 14, 05:45 UTC | 10m |
| 2026-05-13 | FDB1JC | DXB → MUX | May 13, 20:30 UTC | May 13, 20:40 UTC | 10m |
| 2026-05-13 | FDB74X | MUX → DXB | May 13, 06:55 UTC | May 13, 07:05 UTC | 10m |
| 2026-05-13 | FDB9CE | DXB → MUX | May 13, 05:05 UTC | May 13, 05:20 UTC | 15m |
| 2026-05-12 | FDB524 | DAC → DXB | May 12, 16:15 UTC | May 12, 19:35 UTC | 3h 20m |
| 2026-05-12 | FDB523 | DXB → DAC | May 12, 11:55 UTC | May 12, 14:40 UTC | 2h 45m |
| 2026-05-11 | FDB523 | DXB → DAC | May 11, 12:35 UTC | May 12, 12:30 UTC | 23h 56m |
| 2026-05-11 | FDB540 | KTM → DXB | May 11, 11:00 UTC | May 11, 13:00 UTC | 2h 0m |
| 2026-05-10 | FDB9UR | CCU → DXB | May 10, 20:20 UTC | May 11, 09:00 UTC | 12h 40m |
| 2026-05-10 | FDB461 | DXB → CCU | May 10, 16:10 UTC | May 10, 18:49 UTC | 2h 40m |
| 2026-05-10 | FDB9CE | DXB → MUX | May 10, 05:04 UTC | May 10, 05:14 UTC | 10m |
| 2026-05-09 | FDB574 | KTM → DXB | May 9, 17:15 UTC | May 9, 19:00 UTC | 1h 45m |
| 2026-05-09 | FDB573 | DXB → KTM | May 9, 14:20 UTC | May 9, 15:15 UTC | 55m |
| 2026-05-09 | FDB573 | DXB → KTM | May 9, 12:00 UTC | May 9, 12:20 UTC | 20m |
| 2026-05-08 | FDB524 | DAC → DXB | May 8, 16:05 UTC | May 8, 17:20 UTC | 1h 15m |
| 2026-05-08 | FDB523 | DXB → DAC | May 8, 13:50 UTC | May 8, 14:40 UTC | 50m |
| 2026-05-06 | FDB574 | KTM → DXB | May 6, 18:35 UTC | May 7, 12:45 UTC | 18h 10m |
| 2026-05-06 | FDB574 | KTM → DXB | May 6, 17:45 UTC | May 7, 12:45 UTC | 19h 0m |
| 2026-05-06 | FDB573 | DXB → KTM | May 6, 15:25 UTC | May 6, 16:00 UTC | 35m |
| 2026-05-06 | FDB74X | MUX → DXB | May 6, 06:25 UTC | May 6, 06:30 UTC | 5m |
| 2026-05-06 | FDB9CE | DXB → MUX | May 6, 05:00 UTC | May 6, 05:15 UTC | 15m |
| 2026-05-06 | FDB9CE | DXB → MUX | May 6, 02:45 UTC | May 6, 03:05 UTC | 19m |
| 2026-05-05 | FDB808 | JED → DXB | May 5, 16:45 UTC | May 5, 21:40 UTC | 4h 55m |
| 2026-05-04 | FDB75Y | MUX → DXB | May 4, 22:05 UTC | May 4, 22:15 UTC | 10m |
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-FQI page for operator, model, and routing details .