sensors Mode-S transponder
896605
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKO · BOEING 737 MAX 8
- Hex
- 896605
- Octal
- 42263005
- Decimal
- 9,004,549
- Country
- AE
- Tail
- A6-FKO
- Type
- B38M
- Flights observed
- 131
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 896605 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 |
|---|---|---|---|
| FDB1114 | - | 7 | 2026-07-13 |
| FDB1113 | - | 5 | 2026-07-13 |
| FDB3CK | - | 4 | 2026-07-10 |
| FDB1626 | Fly Dubai | 4 | 2026-06-05 |
| FDB870 | Fly Dubai | 3 | 2026-05-20 |
| FDB7KL | Fly Dubai | 3 | 2026-06-13 |
| FDB5PG | Fly Dubai | 3 | 2026-06-09 |
| FDB4XC | - | 3 | 2026-07-13 |
| FDB446 | Fly Dubai | 3 | 2026-04-27 |
| FDB445 | Fly Dubai | 3 | 2026-04-26 |
| FDB1BH | Fly Dubai | 3 | 2026-05-31 |
| FDB1AR | - | 3 | 2026-05-04 |
| FDB1807 | Fly Dubai | 3 | 2026-05-24 |
| FDB176 | Fly Dubai | 3 | 2026-06-12 |
| FDB884 | Fly Dubai | 2 | 2026-05-22 |
| FDB882 | Fly Dubai | 2 | 2026-04-15 |
| FDB881 | Fly Dubai | 2 | 2026-04-15 |
| FDB864 | Fly Dubai | 2 | 2026-06-15 |
| FDB822 | - | 2 | 2026-06-05 |
| FDB7WG | - | 2 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | FDB7XP | - | Jul 14, 09:45 UTC | Jul 14, 14:20 UTC | 4h 35m |
| 2026-07-13 | FDB4XC | - | Jul 13, 19:25 UTC | Jul 14, 04:50 UTC | 9h 25m |
| 2026-07-13 | FDB1114 | - | Jul 13, 13:45 UTC | Jul 13, 16:35 UTC | 2h 50m |
| 2026-07-13 | FDB1113 | - | Jul 13, 09:05 UTC | Jul 13, 12:10 UTC | 3h 5m |
| 2026-07-13 | FDB5PS | - | Jul 13, 02:05 UTC | Jul 13, 05:45 UTC | 3h 40m |
| 2026-07-12 | FDB7WG | - | Jul 12, 21:05 UTC | Jul 13, 00:15 UTC | 3h 10m |
| 2026-07-12 | FDB6 | - | Jul 12, 18:01 UTC | Jul 12, 19:01 UTC | 1h 0m |
| 2026-07-12 | FDB5 | - | Jul 12, 16:01 UTC | Jul 12, 16:45 UTC | 45m |
| 2026-07-12 | FDB833 | - | Jul 12, 07:35 UTC | Jul 12, 13:40 UTC | 6h 5m |
| 2026-07-10 | FDB1HE | - | Jul 10, 19:25 UTC | Jul 10, 22:50 UTC | 3h 25m |
| 2026-07-10 | FDB183 | - | Jul 10, 13:30 UTC | Jul 10, 16:40 UTC | 3h 10m |
| 2026-07-10 | FDB3CK | - | Jul 10, 07:20 UTC | Jul 10, 10:05 UTC | 2h 45m |
| 2026-07-10 | FDB5EX | - | Jul 10, 03:15 UTC | Jul 10, 05:55 UTC | 2h 40m |
| 2026-07-09 | FDB8596 | - | Jul 9, 10:25 UTC | Jul 9, 13:45 UTC | 3h 20m |
| 2026-07-09 | FDB8595 | - | Jul 9, 05:55 UTC | Jul 9, 09:05 UTC | 3h 10m |
| 2026-07-07 | FDB868 | DMM → DXB | Jul 7, 17:00 UTC | Jul 7, 17:55 UTC | 55m |
| 2026-07-07 | FDB867 | - | Jul 7, 14:20 UTC | Jul 7, 15:05 UTC | 45m |
| 2026-07-07 | FDB3UF | MCT → DXB | Jul 7, 06:05 UTC | Jul 7, 06:15 UTC | 10m |
| 2026-07-07 | FDB7HD | - | Jul 7, 03:15 UTC | Jul 7, 03:40 UTC | 25m |
| 2026-07-06 | FDB6 | - | Jul 6, 18:10 UTC | Jul 6, 18:55 UTC | 45m |
| 2026-07-06 | FDB5 | - | Jul 6, 16:10 UTC | Jul 6, 16:50 UTC | 40m |
| 2026-06-15 | FDB864 | DMM → DXB | Jun 15, 12:35 UTC | Jun 15, 13:25 UTC | 50m |
| 2026-06-15 | FDB863 | - | Jun 15, 10:45 UTC | Jun 15, 10:55 UTC | 10m |
| 2026-06-13 | FDB7KL | AMM → DXB | Jun 13, 21:55 UTC | Jun 13, 22:40 UTC | 45m |
| 2026-06-13 | FDB7KL | AMM → DXB | Jun 13, 20:15 UTC | Jun 13, 20:25 UTC | 10m |
| 2026-06-13 | FDB143 | DXB → AMM | Jun 13, 18:45 UTC | Jun 13, 19:00 UTC | 15m |
| 2026-06-12 | FDB176 | HBE → DXB | Jun 12, 21:25 UTC | Jun 13, 17:05 UTC | 19h 39m |
| 2026-06-12 | FDB175 | DXB → HBE | Jun 12, 19:05 UTC | Jun 12, 19:55 UTC | 50m |
| 2026-06-11 | FDB4XC | DXB → MCX | Jun 11, 07:55 UTC | Jun 11, 22:45 UTC | 14h 50m |
| 2026-06-10 | FDB5DN | ISU → DXB | Jun 10, 19:20 UTC | Jun 11, 13:50 UTC | 18h 30m |
| 2026-06-10 | FDB574 | KTM → DXB | Jun 10, 17:55 UTC | Jun 11, 13:50 UTC | 19h 55m |
| 2026-06-10 | FDB3JE | MRV → DXB | Jun 10, 01:50 UTC | Jun 10, 15:25 UTC | 13h 35m |
| 2026-06-09 | FDB5PG | DXB → MRV | Jun 9, 21:15 UTC | Jun 9, 23:20 UTC | 2h 5m |
| 2026-06-07 | FDB1082 | TLV → DXB | Jun 7, 13:15 UTC | Jun 7, 13:40 UTC | 25m |
| 2026-06-07 | FDB1081 | DXB → TLV | Jun 7, 11:05 UTC | Jun 7, 11:30 UTC | 25m |
| 2026-06-07 | FDB5JD | MCX → DXB | Jun 7, 01:15 UTC | Jun 7, 03:00 UTC | 1h 45m |
| 2026-06-06 | FDB4XC | DXB → MCX | Jun 6, 14:14 UTC | Jun 6, 22:34 UTC | 8h 20m |
| 2026-06-05 | FDB822 | - | Jun 5, 19:20 UTC | Jun 6, 19:14 UTC | 23h 55m |
| 2026-06-05 | FDB1626 | TLV → DXB | Jun 5, 18:40 UTC | Jun 6, 14:54 UTC | 20h 15m |
| 2026-06-05 | FDB1626 | TLV → DXB | Jun 5, 16:50 UTC | Jun 6, 14:54 UTC | 22h 5m |
| 2026-06-05 | FDB1625 | DXB → TLV | Jun 5, 14:50 UTC | Jun 5, 15:15 UTC | 25m |
| 2026-06-03 | FDB574 | KTM → DXB | Jun 3, 17:20 UTC | Jun 3, 19:50 UTC | 2h 30m |
| 2026-06-03 | FDB573 | DXB → KTM | Jun 3, 13:15 UTC | Jun 3, 15:25 UTC | 2h 10m |
| 2026-06-03 | FDB5PS | TBS → DXB | Jun 3, 02:25 UTC | Jun 3, 06:40 UTC | 4h 15m |
| 2026-06-02 | FDB7WG | DXB → TBS | Jun 2, 22:20 UTC | Jun 3, 00:10 UTC | 1h 50m |
| 2026-06-02 | FDB16T | BAH → DXB | Jun 2, 13:40 UTC | Jun 2, 14:30 UTC | 50m |
| 2026-06-01 | FDB1626 | TLV → DXB | Jun 1, 19:05 UTC | Jun 1, 19:45 UTC | 40m |
| 2026-06-01 | FDB1626 | TLV → DXB | Jun 1, 17:15 UTC | Jun 1, 17:30 UTC | 15m |
| 2026-05-31 | FDB1625 | DXB → TLV | May 31, 21:30 UTC | Jun 1, 15:30 UTC | 18h 0m |
| 2026-05-31 | FDB7KL | AMM → DXB | May 31, 19:50 UTC | May 31, 20:00 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-FKO page for operator, model, and routing details .