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