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