sensors Mode-S transponder
8965CC
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKA · BOEING 737 MAX 8
- Hex
- 8965CC
- Octal
- 42262714
- Decimal
- 9,004,492
- Country
- AE
- Tail
- A6-FKA
- Type
- B38M
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 58m ago
Last known position
Country allocation
The ICAO 24-bit address 8965CC 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 |
|---|---|---|---|
| FDB884 | - | 4 | 2026-06-23 |
| FDB882 | Fly Dubai | 4 | 2026-06-19 |
| FDB646 | Fly Dubai | 4 | 2026-06-18 |
| FDB883 | - | 3 | 2026-06-23 |
| FDB59J | Fly Dubai | 3 | 2026-05-18 |
| FDB307 | - | 3 | 2026-06-22 |
| FDB870 | Fly Dubai | 2 | 2026-06-07 |
| FDB822 | - | 2 | 2026-05-16 |
| FDB821 | Fly Dubai | 2 | 2026-06-16 |
| FDB811 | Fly Dubai | 2 | 2026-06-04 |
| FDB2PE | Fly Dubai | 2 | 2026-05-22 |
| FDB9CE | Fly Dubai | 1 | 2026-06-04 |
| FDB920 | Fly Dubai | 1 | 2026-05-19 |
| FDB906 | Fly Dubai | 1 | 2026-05-25 |
| FDB881 | - | 1 | 2026-06-21 |
| FDB876 | Fly Dubai | 1 | 2026-06-09 |
| FDB8708 | - | 1 | 2026-04-30 |
| FDB8499 | - | 1 | 2026-06-18 |
| FDB827 | - | 1 | 2026-06-20 |
| FDB812 | Fly Dubai | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-23 | FDB884 | - | Jun 23, 05:39 UTC | Jun 23, 06:29 UTC | 50m |
| 2026-06-23 | FDB883 | - | Jun 23, 03:09 UTC | Jun 23, 04:09 UTC | 1h 0m |
| 2026-06-22 | FDB308 | - | Jun 22, 12:54 UTC | Jun 22, 15:05 UTC | 2h 10m |
| 2026-06-22 | FDB307 | - | Jun 22, 08:00 UTC | Jun 22, 08:19 UTC | 20m |
| 2026-06-21 | FDB881 | - | Jun 21, 11:20 UTC | Jun 21, 12:10 UTC | 50m |
| 2026-06-21 | FDB2GT | - | Jun 21, 08:25 UTC | Jun 21, 08:35 UTC | 10m |
| 2026-06-21 | FDB1KF | - | Jun 21, 03:40 UTC | Jun 21, 03:59 UTC | 20m |
| 2026-06-20 | FDB827 | - | Jun 20, 18:19 UTC | Jun 20, 23:39 UTC | 5h 20m |
| 2026-06-20 | FDB307 | - | Jun 20, 08:14 UTC | Jun 20, 08:39 UTC | 25m |
| 2026-06-19 | FDB882 | TUU → DXB | Jun 19, 11:20 UTC | Jun 19, 18:44 UTC | 7h 25m |
| 2026-06-18 | FDB646 | ASM → DXB | Jun 18, 15:40 UTC | Jun 18, 23:35 UTC | 7h 55m |
| 2026-06-18 | FDB8499 | - | Jun 18, 02:15 UTC | Jun 18, 09:25 UTC | 7h 10m |
| 2026-06-17 | FDB307 | - | Jun 17, 08:00 UTC | Jun 17, 08:20 UTC | 20m |
| 2026-06-16 | FDB821 | DXB → HAS | Jun 16, 10:09 UTC | Jun 16, 15:05 UTC | 4h 55m |
| 2026-06-15 | FDB884 | - | Jun 15, 05:50 UTC | Jun 15, 06:55 UTC | 1h 5m |
| 2026-06-15 | FDB883 | - | Jun 15, 04:00 UTC | Jun 15, 04:15 UTC | 15m |
| 2026-06-13 | FDB574 | KTM → DXB | Jun 13, 17:45 UTC | Jun 13, 18:30 UTC | 45m |
| 2026-06-12 | FDB573 | DXB → KTM | Jun 12, 21:50 UTC | Jun 13, 16:00 UTC | 18h 9m |
| 2026-06-12 | FDB646 | ASM → DXB | Jun 12, 16:05 UTC | Jun 13, 15:00 UTC | 22h 54m |
| 2026-06-12 | FDB646 | ASM → DXB | Jun 12, 08:30 UTC | Jun 12, 22:35 UTC | 14h 5m |
| 2026-06-10 | FDB882 | TUU → DXB | Jun 10, 17:40 UTC | Jun 10, 18:05 UTC | 25m |
| 2026-06-10 | FDB884 | DMM → DXB | Jun 10, 05:45 UTC | Jun 10, 06:50 UTC | 1h 5m |
| 2026-06-09 | FDB876 | TIF → DXB | Jun 9, 17:10 UTC | Jun 9, 17:45 UTC | 35m |
| 2026-06-09 | FDB64X | BAH → DXB | Jun 9, 09:35 UTC | Jun 9, 10:20 UTC | 45m |
| 2026-06-08 | FDB1636 | TLV → DXB | Jun 8, 15:35 UTC | Jun 8, 16:20 UTC | 45m |
| 2026-06-07 | FDB870 | DMM → DXB | Jun 7, 11:10 UTC | Jun 8, 10:05 UTC | 22h 55m |
| 2026-06-07 | FDB870 | DMM → DXB | Jun 7, 10:50 UTC | Jun 7, 11:55 UTC | 1h 5m |
| 2026-06-05 | FDB882 | TUU → DXB | Jun 5, 12:05 UTC | Jun 5, 17:45 UTC | 5h 40m |
| 2026-06-04 | FDB811 | DXB → AHB | Jun 4, 12:50 UTC | Jun 4, 13:00 UTC | 10m |
| 2026-06-04 | FDB74X | MUX → DXB | Jun 4, 06:25 UTC | Jun 4, 06:30 UTC | 5m |
| 2026-06-04 | FDB9CE | DXB → MUX | Jun 4, 05:00 UTC | Jun 4, 05:10 UTC | 10m |
| 2026-06-03 | FDB5JD | MCX → DXB | Jun 3, 00:50 UTC | Jun 3, 17:45 UTC | 16h 55m |
| 2026-06-02 | FDB4XC | DXB → MCX | Jun 2, 20:55 UTC | Jun 2, 22:40 UTC | 1h 45m |
| 2026-06-01 | FDB882 | TUU → DXB | Jun 1, 17:05 UTC | Jun 1, 17:35 UTC | 30m |
| 2026-06-01 | FDB884 | DMM → DXB | Jun 1, 05:40 UTC | Jun 1, 06:40 UTC | 1h 0m |
| 2026-06-01 | FDB883 | DXB → DMM | Jun 1, 03:15 UTC | Jun 1, 04:05 UTC | 50m |
| 2026-05-29 | FDB812 | AHB → DXB | May 29, 17:15 UTC | May 29, 17:30 UTC | 15m |
| 2026-05-28 | FDB821 | DXB → HAS | May 28, 10:25 UTC | May 28, 10:35 UTC | 10m |
| 2026-05-25 | FDB906 | ULH → DXB | May 25, 16:35 UTC | May 25, 17:15 UTC | 40m |
| 2026-05-24 | FDB1BH | TBS → DXB | May 24, 08:45 UTC | May 24, 12:30 UTC | 3h 45m |
| 2026-05-23 | FDB71T | TBS → DXB | May 23, 12:30 UTC | May 24, 06:10 UTC | 17h 40m |
| 2026-05-22 | FDB2PE | BEY → DXB | May 22, 15:45 UTC | May 23, 10:20 UTC | 18h 34m |
| 2026-05-22 | FDB2PE | BEY → DXB | May 22, 11:40 UTC | May 23, 10:20 UTC | 22h 39m |
| 2026-05-20 | FDB176 | HBE → DXB | May 20, 21:05 UTC | May 20, 21:30 UTC | 25m |
| 2026-05-19 | FDB920 | JED → DXB | May 19, 03:10 UTC | May 19, 03:40 UTC | 30m |
| 2026-05-18 | FDB59J | BAH → DXB | May 18, 16:30 UTC | May 18, 17:20 UTC | 50m |
| 2026-05-16 | FDB822 | - | May 16, 14:05 UTC | May 17, 04:45 UTC | 14h 40m |
| 2026-05-15 | FDB822 | - | May 15, 17:30 UTC | May 16, 14:46 UTC | 21h 16m |
| 2026-05-13 | FDB646 | ASM → DXB | May 13, 21:55 UTC | May 14, 14:25 UTC | 16h 30m |
| 2026-05-13 | FDB645 | DXB → ASM | May 13, 15:05 UTC | May 13, 15:15 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-FKA page for operator, model, and routing details .