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