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