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