sensors Mode-S transponder
8965D5
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKJ · BOEING 737 MAX 8
- Hex
- 8965D5
- Octal
- 42262725
- Decimal
- 9,004,501
- Country
- AE
- Tail
- A6-FKJ
- Type
- B38M
- Flights observed
- 74
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 8965D5 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 | 5 | 2026-04-21 |
| FDB3TH | Fly Dubai | 5 | 2026-05-13 |
| FDB16T | Fly Dubai | 4 | 2026-05-13 |
| FDB1YT | Fly Dubai | 3 | 2026-04-21 |
| FDB9RF | Fly Dubai | 2 | 2026-04-17 |
| FDB809 | Fly Dubai | 2 | 2026-04-20 |
| FDB7ZK | Fly Dubai | 2 | 2026-05-28 |
| FDB646 | Fly Dubai | 2 | 2026-05-10 |
| FDB574 | Fly Dubai | 2 | 2026-05-25 |
| FDB454 | Fly Dubai | 2 | 2026-04-18 |
| FDB430 | Fly Dubai | 2 | 2026-04-25 |
| FDB2JQ | Fly Dubai | 2 | 2026-04-24 |
| FDB9FX | Fly Dubai | 1 | 2026-05-14 |
| FDB94F | Fly Dubai | 1 | 2026-04-28 |
| FDB947 | Fly Dubai | 1 | 2026-05-01 |
| FDB920 | Fly Dubai | 1 | 2026-05-22 |
| FDB905 | Fly Dubai | 1 | 2026-04-28 |
| FDB884 | Fly Dubai | 1 | 2026-05-18 |
| FDB882 | Fly Dubai | 1 | 2026-05-11 |
| FDB864 | Fly Dubai | 1 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1ZA | SPX → DXB | May 29, 23:10 UTC | May 30, 01:40 UTC | 2h 30m |
| 2026-05-29 | FDB4RM | DXB → SPX | May 29, 10:10 UTC | May 29, 21:20 UTC | 11h 10m |
| 2026-05-28 | FDB7ZK | DOH → DXB | May 28, 15:55 UTC | May 28, 16:40 UTC | 45m |
| 2026-05-27 | FDB71T | TBS → DXB | May 27, 12:35 UTC | May 28, 05:45 UTC | 17h 10m |
| 2026-05-26 | FDB176 | HBE → DXB | May 26, 13:04 UTC | May 27, 00:19 UTC | 11h 15m |
| 2026-05-25 | FDB5DN | ISU → DXB | May 25, 21:19 UTC | May 26, 17:09 UTC | 19h 50m |
| 2026-05-25 | FDB574 | KTM → DXB | May 25, 19:20 UTC | May 26, 17:09 UTC | 21h 50m |
| 2026-05-25 | FDB574 | KTM → DXB | May 25, 19:10 UTC | May 26, 17:09 UTC | 22h 0m |
| 2026-05-25 | FDB573 | DXB → KTM | May 25, 09:20 UTC | May 25, 17:45 UTC | 8h 25m |
| 2026-05-25 | FDB3CK | AMM → DXB | May 25, 07:40 UTC | May 25, 07:50 UTC | 10m |
| 2026-05-24 | FDB7UE | EVN → DXB | May 24, 08:35 UTC | May 24, 11:40 UTC | 3h 5m |
| 2026-05-23 | FDB628 | BJV → DXB | May 23, 13:00 UTC | May 23, 16:40 UTC | 3h 40m |
| 2026-05-23 | FDB4XE | DXB → BJV | May 23, 03:05 UTC | May 23, 11:30 UTC | 8h 25m |
| 2026-05-22 | FDB920 | JED → DXB | May 22, 13:05 UTC | May 23, 11:15 UTC | 22h 10m |
| 2026-05-21 | FDB75L | BAH → DXB | May 21, 12:55 UTC | May 21, 13:55 UTC | 1h 0m |
| 2026-05-20 | - | - | May 20, 09:55 UTC | May 21, 03:50 UTC | 17h 55m |
| 2026-05-18 | FDB884 | DMM → DXB | May 18, 05:35 UTC | May 18, 06:35 UTC | 1h 0m |
| 2026-05-16 | FDB7KL | AMM → DXB | May 16, 16:31 UTC | May 17, 09:55 UTC | 17h 25m |
| 2026-05-14 | FDB9FX | SKT → DXB | May 14, 22:45 UTC | May 15, 02:50 UTC | 4h 5m |
| 2026-05-14 | FDB4DT | DXB → SKT | May 14, 20:45 UTC | May 14, 21:10 UTC | 25m |
| 2026-05-13 | FDB16T | BAH → DXB | May 13, 14:20 UTC | May 13, 15:20 UTC | 1h 0m |
| 2026-05-13 | FDB3TH | DXB → BAH | May 13, 12:05 UTC | May 13, 12:55 UTC | 50m |
| 2026-05-11 | FDB882 | TUU → DXB | May 11, 12:15 UTC | May 11, 17:25 UTC | 5h 10m |
| 2026-05-10 | FDB646 | ASM → DXB | May 10, 22:09 UTC | May 11, 17:25 UTC | 19h 16m |
| 2026-05-10 | FDB646 | ASM → DXB | May 10, 16:00 UTC | May 11, 12:15 UTC | 20h 15m |
| 2026-05-08 | FDB64X | - | May 8, 10:25 UTC | May 8, 10:49 UTC | 25m |
| 2026-05-05 | FDB812A | - | May 5, 19:15 UTC | May 6, 12:40 UTC | 17h 25m |
| 2026-05-04 | FDB811 | DXB → AHB | May 4, 12:10 UTC | May 4, 13:10 UTC | 1h 0m |
| 2026-05-03 | FDB605 | DXB → ADD | May 3, 21:54 UTC | May 4, 07:10 UTC | 9h 15m |
| 2026-05-03 | FDB16T | BAH → DXB | May 3, 14:05 UTC | May 3, 15:00 UTC | 55m |
| 2026-05-03 | FDB3TH | DXB → BAH | May 3, 11:45 UTC | May 3, 12:35 UTC | 50m |
| 2026-05-02 | FDB864 | DMM → DXB | May 2, 12:40 UTC | May 2, 13:35 UTC | 55m |
| 2026-05-02 | FDB863 | DXB → DMM | May 2, 10:00 UTC | May 2, 11:00 UTC | 1h 0m |
| 2026-05-02 | FDB62H | KHI → DXB | May 2, 01:25 UTC | May 2, 01:55 UTC | 30m |
| 2026-05-01 | FDB7HU | DXB → KHI | May 1, 20:55 UTC | May 1, 21:20 UTC | 25m |
| 2026-05-01 | FDB947 | DXB → AQI | May 1, 07:35 UTC | May 1, 12:50 UTC | 5h 15m |
| 2026-04-30 | FDB3YX | DXB → KHI | Apr 30, 08:35 UTC | Apr 30, 13:30 UTC | 4h 55m |
| 2026-04-29 | FDB16T | BAH → DXB | Apr 29, 13:55 UTC | Apr 29, 14:45 UTC | 50m |
| 2026-04-29 | FDB3TH | DXB → BAH | Apr 29, 11:45 UTC | Apr 29, 12:30 UTC | 45m |
| 2026-04-28 | FDB905 | DXB → ULH | Apr 28, 15:55 UTC | Apr 28, 22:20 UTC | 6h 25m |
| 2026-04-28 | FDB5JN | MCT → DXB | Apr 28, 09:55 UTC | Apr 28, 10:25 UTC | 30m |
| 2026-04-28 | FDB94F | DXB → MCT | Apr 28, 07:25 UTC | Apr 28, 07:45 UTC | 20m |
| 2026-04-27 | FDB2UB | LYP → DXB | Apr 27, 23:20 UTC | Apr 28, 01:55 UTC | 2h 35m |
| 2026-04-27 | FDB355 | DXB → LYP | Apr 27, 19:00 UTC | Apr 27, 19:20 UTC | 20m |
| 2026-04-25 | FDB430 | CCJ → DXB | Apr 25, 04:00 UTC | Apr 25, 06:15 UTC | 2h 15m |
| 2026-04-24 | FDB2JQ | DXB → CCJ | Apr 24, 22:05 UTC | Apr 25, 00:15 UTC | 2h 10m |
| 2026-04-23 | FDB16T | BAH → DXB | Apr 23, 15:10 UTC | Apr 23, 16:25 UTC | 1h 15m |
| 2026-04-23 | FDB3TH | DXB → BAH | Apr 23, 13:15 UTC | Apr 23, 13:40 UTC | 25m |
| 2026-04-23 | FDB3TH | DXB → BAH | Apr 23, 11:35 UTC | Apr 23, 12:30 UTC | 55m |
| 2026-04-22 | FDB7ZK | DOH → DXB | Apr 22, 16:40 UTC | Apr 22, 17:55 UTC | 1h 15m |
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-FKJ page for operator, model, and routing details .