sensors Mode-S transponder
8965D4
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKI · BOEING 737 MAX 8
- Hex
- 8965D4
- Octal
- 42262724
- Decimal
- 9,004,500
- Country
- AE
- Tail
- A6-FKI
- Type
- B38M
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 8965D4 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 |
|---|---|---|---|
| FDB4JZ | Fly Dubai | 8 | 2026-04-16 |
| FDB1YT | Fly Dubai | 6 | 2026-04-16 |
| FDB3TH | Fly Dubai | 4 | 2026-05-06 |
| FDB864 | Fly Dubai | 3 | 2026-05-14 |
| FDB64X | - | 3 | 2026-05-19 |
| FDB16T | Fly Dubai | 3 | 2026-05-06 |
| FDB881 | Fly Dubai | 2 | 2026-05-18 |
| FDB828 | Fly Dubai | 2 | 2026-04-17 |
| FDB827 | Fly Dubai | 2 | 2026-04-18 |
| FDB5WB | Fly Dubai | 2 | 2026-04-28 |
| FDB5JA | Fly Dubai | 2 | 2026-04-28 |
| FDB564 | Fly Dubai | 2 | 2026-04-15 |
| FDB563 | Fly Dubai | 2 | 2026-04-15 |
| FDB2UB | Fly Dubai | 2 | 2026-05-02 |
| FDB1AR | - | 2 | 2026-05-01 |
| FDB1212 | Fly Dubai | 2 | 2026-05-24 |
| FDB9QG | Fly Dubai | 1 | 2026-05-04 |
| FDB9FX | Fly Dubai | 1 | 2026-05-03 |
| FDB948 | Fly Dubai | 1 | 2026-05-05 |
| FDB932 | Fly Dubai | 1 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FDB3DY | DXB → TBS | May 30, 09:15 UTC | May 30, 12:05 UTC | 2h 50m |
| 2026-05-28 | FDB3JE | MRV → DXB | May 28, 20:00 UTC | May 29, 10:55 UTC | 14h 55m |
| 2026-05-26 | FDB71T | TBS → DXB | May 26, 13:10 UTC | May 26, 16:45 UTC | 3h 35m |
| 2026-05-25 | FDB2WK | DXB → TBS | May 25, 15:40 UTC | May 26, 10:44 UTC | 19h 4m |
| 2026-05-25 | FDB580 | CMB → DXB | May 25, 04:25 UTC | May 25, 15:55 UTC | 11h 30m |
| 2026-05-24 | FDB1212 | TLV → DXB | May 24, 13:20 UTC | May 25, 02:25 UTC | 13h 5m |
| 2026-05-24 | FDB1212 | TLV → DXB | May 24, 11:30 UTC | May 24, 11:50 UTC | 20m |
| 2026-05-24 | FDB1211 | DXB → TLV | May 24, 09:15 UTC | May 24, 09:45 UTC | 30m |
| 2026-05-23 | FDB822 | - | May 23, 14:05 UTC | May 24, 09:45 UTC | 19h 40m |
| 2026-05-23 | FDB5PS | TBS → DXB | May 23, 01:55 UTC | May 23, 14:45 UTC | 12h 49m |
| 2026-05-22 | FDB7WG | DXB → TBS | May 22, 14:05 UTC | May 23, 00:35 UTC | 10h 30m |
| 2026-05-21 | FDB574 | KTM → DXB | May 21, 18:45 UTC | May 22, 09:40 UTC | 14h 55m |
| 2026-05-21 | FDB573 | DXB → KTM | May 21, 15:55 UTC | May 21, 16:50 UTC | 55m |
| 2026-05-20 | FDB1082 | TLV → DXB | May 20, 14:00 UTC | May 20, 14:15 UTC | 15m |
| 2026-05-19 | FDB64X | - | May 19, 09:30 UTC | May 19, 10:25 UTC | 55m |
| 2026-05-18 | FDB881 | DXB → TUU | May 18, 12:10 UTC | May 18, 12:20 UTC | 10m |
| 2026-05-16 | FDB812 | AHB → DXB | May 16, 05:10 UTC | May 16, 17:15 UTC | 12h 6m |
| 2026-05-14 | FDB864 | DMM → DXB | May 14, 12:50 UTC | May 14, 13:40 UTC | 50m |
| 2026-05-13 | FDB870 | DMM → DXB | May 13, 10:10 UTC | May 13, 10:50 UTC | 40m |
| 2026-05-12 | FDB906 | ULH → DXB | May 12, 16:45 UTC | May 12, 17:10 UTC | 25m |
| 2026-05-10 | FDB932 | NUM → DXB | May 10, 09:30 UTC | May 11, 01:25 UTC | 15h 55m |
| 2026-05-09 | FDB864 | DMM → DXB | May 9, 12:35 UTC | May 9, 13:35 UTC | 1h 0m |
| 2026-05-08 | FDB176 | HBE → DXB | May 8, 21:00 UTC | May 9, 00:05 UTC | 3h 5m |
| 2026-05-08 | FDB175 | DXB → HBE | May 8, 16:20 UTC | May 8, 19:25 UTC | 3h 5m |
| 2026-05-06 | FDB16T | BAH → DXB | May 6, 15:35 UTC | May 6, 16:55 UTC | 1h 20m |
| 2026-05-06 | FDB3TH | DXB → BAH | May 6, 13:55 UTC | May 6, 14:10 UTC | 15m |
| 2026-05-05 | FDB948 | AQI → DXB | May 5, 08:05 UTC | May 5, 13:25 UTC | 5h 20m |
| 2026-05-04 | FDB9QG | KHI → DXB | May 4, 20:35 UTC | May 4, 21:15 UTC | 40m |
| 2026-05-03 | FDB9FX | SKT → DXB | May 3, 22:45 UTC | May 4, 03:35 UTC | 4h 50m |
| 2026-05-03 | FDB4DT | DXB → SKT | May 3, 20:40 UTC | May 3, 21:00 UTC | 20m |
| 2026-05-03 | FDB864 | DMM → DXB | May 3, 12:35 UTC | May 3, 13:35 UTC | 1h 0m |
| 2026-05-03 | FDB863 | DXB → DMM | May 3, 10:10 UTC | May 3, 11:10 UTC | 1h 0m |
| 2026-05-02 | FDB2UB | LYP → DXB | May 2, 23:25 UTC | May 2, 23:35 UTC | 10m |
| 2026-05-02 | FDB75L | BAH → DXB | May 2, 12:55 UTC | May 2, 13:45 UTC | 50m |
| 2026-05-02 | FDB15L | DXB → BAH | May 2, 10:30 UTC | May 2, 11:20 UTC | 50m |
| 2026-05-01 | FDB2UB | LYP → DXB | May 1, 21:30 UTC | May 2, 02:30 UTC | 5h 0m |
| 2026-05-01 | FDB355 | DXB → LYP | May 1, 19:20 UTC | May 1, 19:40 UTC | 20m |
| 2026-05-01 | FDB64X | - | May 1, 10:05 UTC | May 1, 10:55 UTC | 50m |
| 2026-05-01 | FDB1AR | - | May 1, 07:45 UTC | May 1, 08:35 UTC | 50m |
| 2026-04-30 | FDB16T | BAH → DXB | Apr 30, 14:25 UTC | Apr 30, 15:10 UTC | 45m |
| 2026-04-30 | FDB3TH | DXB → BAH | Apr 30, 11:50 UTC | Apr 30, 12:40 UTC | 50m |
| 2026-04-28 | FDB5WB | BEY → DXB | Apr 28, 12:10 UTC | Apr 28, 15:25 UTC | 3h 15m |
| 2026-04-28 | FDB5JA | DXB → BEY | Apr 28, 06:35 UTC | Apr 28, 07:45 UTC | 1h 10m |
| 2026-04-27 | FDB64X | - | Apr 27, 11:15 UTC | Apr 27, 12:05 UTC | 50m |
| 2026-04-27 | FDB1AR | - | Apr 27, 07:15 UTC | Apr 27, 08:00 UTC | 45m |
| 2026-04-26 | FDB881 | DXB → TUU | Apr 26, 11:45 UTC | Apr 26, 18:55 UTC | 7h 10m |
| 2026-04-24 | FDB16T | BAH → DXB | Apr 24, 14:10 UTC | Apr 24, 15:45 UTC | 1h 35m |
| 2026-04-24 | FDB3TH | DXB → BAH | Apr 24, 12:25 UTC | Apr 24, 12:45 UTC | 20m |
| 2026-04-24 | FDB3TH | DXB → BAH | Apr 24, 10:30 UTC | Apr 24, 11:35 UTC | 1h 5m |
| 2026-04-23 | FDB5WB | BEY → DXB | Apr 23, 06:50 UTC | Apr 23, 15:15 UTC | 8h 25m |
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-FKI page for operator, model, and routing details .