sensors Mode-S transponder
8965D6
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKK · BOEING 737 MAX 8
- Hex
- 8965D6
- Octal
- 42262726
- Decimal
- 9,004,502
- Country
- AE
- Tail
- A6-FKK
- Type
- B38M
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 48m ago
Last known position
Country allocation
The ICAO 24-bit address 8965D6 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 |
|---|---|---|---|
| FDB176 | Fly Dubai | 6 | 2026-06-01 |
| FDB175 | Fly Dubai | 5 | 2026-06-01 |
| FDB811 | Fly Dubai | 3 | 2026-05-10 |
| FDB7XZ | Fly Dubai | 3 | 2026-05-29 |
| FDB7KL | Fly Dubai | 3 | 2026-05-29 |
| FDB864 | Fly Dubai | 2 | 2026-06-07 |
| FDB812 | Fly Dubai | 2 | 2026-05-03 |
| FDB662 | Fly Dubai | 2 | 2026-06-04 |
| FDB39K | Fly Dubai | 2 | 2026-05-28 |
| FDB2GT | Fly Dubai | 2 | 2026-05-04 |
| FDB1BH | Fly Dubai | 2 | 2026-06-05 |
| FDB1AR | - | 2 | 2026-04-28 |
| FDB143 | Fly Dubai | 2 | 2026-05-29 |
| FDB9CE | Fly Dubai | 1 | 2026-05-27 |
| FDB947 | Fly Dubai | 1 | 2026-04-24 |
| FDB9005 | - | 1 | 2026-04-20 |
| FDB884 | Fly Dubai | 1 | 2026-05-01 |
| FDB883 | Fly Dubai | 1 | 2026-05-01 |
| FDB882 | Fly Dubai | 1 | 2026-06-04 |
| FDB828 | Fly Dubai | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | FDB17 | - | Jun 8, 12:45 UTC | Jun 8, 12:50 UTC | 5m |
| 2026-06-07 | FDB864 | DMM → DXB | Jun 7, 13:35 UTC | Jun 7, 14:20 UTC | 45m |
| 2026-06-05 | FDB1BH | TBS → DXB | Jun 5, 08:50 UTC | Jun 5, 09:20 UTC | 30m |
| 2026-06-05 | FDB4XN | DXB → TBS | Jun 5, 06:00 UTC | Jun 5, 06:10 UTC | 10m |
| 2026-06-04 | FDB882 | TUU → DXB | Jun 4, 12:10 UTC | Jun 5, 03:30 UTC | 15h 20m |
| 2026-06-04 | FDB662 | HGA → DXB | Jun 4, 07:55 UTC | Jun 4, 08:20 UTC | 25m |
| 2026-06-03 | FDB662 | HGA → DXB | Jun 3, 12:55 UTC | Jun 4, 08:20 UTC | 19h 25m |
| 2026-06-01 | FDB176 | HBE → DXB | Jun 1, 21:20 UTC | Jun 2, 11:40 UTC | 14h 20m |
| 2026-06-01 | FDB175 | DXB → HBE | Jun 1, 19:10 UTC | Jun 1, 19:25 UTC | 15m |
| 2026-06-01 | FDB1722 | ALA → DXB | Jun 1, 03:25 UTC | Jun 1, 03:50 UTC | 25m |
| 2026-05-31 | FDB1211 | DXB → TLV | May 31, 09:35 UTC | May 31, 10:00 UTC | 25m |
| 2026-05-29 | FDB7KL | AMM → DXB | May 29, 21:25 UTC | May 29, 22:05 UTC | 40m |
| 2026-05-29 | FDB7KL | AMM → DXB | May 29, 19:40 UTC | May 29, 19:55 UTC | 15m |
| 2026-05-29 | FDB143 | DXB → AMM | May 29, 17:55 UTC | May 29, 18:10 UTC | 15m |
| 2026-05-29 | FDB7XZ | BGW → DXB | May 29, 06:20 UTC | May 29, 16:10 UTC | 9h 50m |
| 2026-05-28 | FDB7XZ | BGW → DXB | May 28, 15:55 UTC | May 29, 12:25 UTC | 20h 30m |
| 2026-05-28 | FDB7XZ | BGW → DXB | May 28, 15:30 UTC | May 29, 12:25 UTC | 20h 55m |
| 2026-05-28 | FDB2PE | BEY → DXB | May 28, 11:35 UTC | May 29, 06:30 UTC | 18h 55m |
| 2026-05-28 | FDB39K | DXB → BEY | May 28, 11:20 UTC | May 29, 06:30 UTC | 19h 10m |
| 2026-05-27 | FDB39K | DXB → BEY | May 27, 21:35 UTC | May 28, 16:05 UTC | 18h 30m |
| 2026-05-27 | FDB176 | HBE → DXB | May 27, 20:55 UTC | May 28, 16:05 UTC | 19h 10m |
| 2026-05-27 | FDB74X | MUX → DXB | May 27, 06:40 UTC | May 27, 06:44 UTC | 5m |
| 2026-05-27 | FDB9CE | DXB → MUX | May 27, 05:14 UTC | May 27, 05:24 UTC | 10m |
| 2026-05-25 | FDB828 | MED → DXB | May 25, 22:55 UTC | May 26, 14:14 UTC | 15h 20m |
| 2026-05-24 | FDB5JD | MCX → DXB | May 24, 04:15 UTC | May 24, 12:45 UTC | 8h 30m |
| 2026-05-23 | FDB1BH | TBS → DXB | May 23, 08:40 UTC | May 23, 22:15 UTC | 13h 36m |
| 2026-05-22 | FDB7KL | AMM → DXB | May 22, 21:40 UTC | May 23, 06:10 UTC | 8h 29m |
| 2026-05-22 | FDB143 | DXB → AMM | May 22, 18:25 UTC | May 22, 18:35 UTC | 10m |
| 2026-05-21 | FDB176 | HBE → DXB | May 21, 21:35 UTC | May 22, 16:40 UTC | 19h 5m |
| 2026-05-21 | FDB176 | HBE → DXB | May 21, 21:20 UTC | May 22, 16:40 UTC | 19h 20m |
| 2026-05-18 | FDB176 | HBE → DXB | May 18, 20:55 UTC | May 19, 12:55 UTC | 16h 0m |
| 2026-05-18 | FDB175 | DXB → HBE | May 18, 18:30 UTC | May 18, 19:25 UTC | 55m |
| 2026-05-17 | FDB175 | DXB → HBE | May 17, 21:35 UTC | May 18, 19:25 UTC | 21h 49m |
| 2026-05-17 | FDB175 | DXB → HBE | May 17, 21:01 UTC | May 18, 19:25 UTC | 22h 24m |
| 2026-05-16 | FDB864 | DMM → DXB | May 16, 15:01 UTC | May 16, 15:55 UTC | 55m |
| 2026-05-12 | FDB4DT | DXB → SKT | May 12, 22:45 UTC | May 13, 01:25 UTC | 2h 40m |
| 2026-05-10 | FDB811 | DXB → AHB | May 10, 12:54 UTC | May 10, 17:15 UTC | 4h 20m |
| 2026-05-07 | FDB5DN | ISU → DXB | May 7, 13:50 UTC | May 7, 14:30 UTC | 40m |
| 2026-05-04 | FDB2GT | KHI → DXB | May 4, 14:25 UTC | May 5, 08:40 UTC | 18h 16m |
| 2026-05-04 | FDB307 | DXB → KBL | May 4, 08:00 UTC | May 4, 08:30 UTC | 30m |
| 2026-05-03 | FDB812 | AHB → DXB | May 3, 12:20 UTC | May 3, 18:25 UTC | 6h 5m |
| 2026-05-03 | FDB2GT | KHI → DXB | May 3, 08:15 UTC | May 3, 08:40 UTC | 25m |
| 2026-05-02 | FDB812 | AHB → DXB | May 2, 17:25 UTC | May 2, 18:25 UTC | 1h 0m |
| 2026-05-02 | FDB811 | DXB → AHB | May 2, 12:05 UTC | May 2, 13:05 UTC | 1h 0m |
| 2026-05-01 | FDB176 | HBE → DXB | May 1, 21:05 UTC | May 2, 00:45 UTC | 3h 40m |
| 2026-05-01 | FDB175 | DXB → HBE | May 1, 15:10 UTC | May 1, 19:25 UTC | 4h 15m |
| 2026-05-01 | FDB884 | DMM → DXB | May 1, 05:40 UTC | May 1, 06:30 UTC | 50m |
| 2026-05-01 | FDB883 | DXB → DMM | May 1, 03:20 UTC | May 1, 04:05 UTC | 45m |
| 2026-04-28 | FDB1YT | BAH → DXB | Apr 28, 10:00 UTC | Apr 28, 11:00 UTC | 1h 0m |
| 2026-04-28 | FDB1AR | - | Apr 28, 07:35 UTC | Apr 28, 08:25 UTC | 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-FKK page for operator, model, and routing details .