sensors Mode-S transponder
8965CE
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKC · BOEING 737 MAX 8
- Hex
- 8965CE
- Octal
- 42262716
- Decimal
- 9,004,494
- Country
- AE
- Tail
- A6-FKC
- Type
- B38M
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 8965CE 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 |
|---|---|---|---|
| FDB1082 | Fly Dubai | 4 | 2026-05-19 |
| FDB7KL | Fly Dubai | 3 | 2026-05-24 |
| FDB760 | Fly Dubai | 3 | 2026-05-29 |
| FDB9RF | Fly Dubai | 2 | 2026-04-24 |
| FDB864 | Fly Dubai | 2 | 2026-05-23 |
| FDB75L | Fly Dubai | 2 | 2026-04-29 |
| FDB64X | - | 2 | 2026-05-11 |
| FDB4JZ | Fly Dubai | 2 | 2026-04-17 |
| FDB4DT | Fly Dubai | 2 | 2026-05-13 |
| FDB454 | Fly Dubai | 2 | 2026-04-24 |
| FDB3YX | Fly Dubai | 2 | 2026-05-05 |
| FDB1YT | Fly Dubai | 2 | 2026-04-17 |
| FDB1AR | - | 2 | 2026-04-18 |
| FDB15L | Fly Dubai | 2 | 2026-04-29 |
| FDB1081 | Fly Dubai | 2 | 2026-05-19 |
| FDB9RQ | Fly Dubai | 1 | 2026-05-23 |
| FDB9QG | Fly Dubai | 1 | 2026-04-22 |
| FDB9FX | Fly Dubai | 1 | 2026-04-30 |
| FDB948 | Fly Dubai | 1 | 2026-05-12 |
| FDB920 | Fly Dubai | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FDB1BH | TBS → DXB | Jun 2, 09:10 UTC | Jun 2, 22:00 UTC | 12h 50m |
| 2026-06-01 | FDB4XN | DXB → TBS | Jun 1, 11:50 UTC | Jun 2, 06:30 UTC | 18h 40m |
| 2026-05-31 | FDB4RM | DXB → SPX | May 31, 18:10 UTC | May 31, 21:40 UTC | 3h 30m |
| 2026-05-30 | FDB5PG | DXB → MRV | May 30, 10:15 UTC | May 30, 22:05 UTC | 11h 50m |
| 2026-05-29 | FDB760 | AYT → DXB | May 29, 16:30 UTC | May 30, 10:15 UTC | 17h 45m |
| 2026-05-29 | FDB760 | AYT → DXB | May 29, 01:25 UTC | May 29, 17:10 UTC | 15h 45m |
| 2026-05-28 | FDB760 | AYT → DXB | May 28, 20:30 UTC | May 29, 17:10 UTC | 20h 41m |
| 2026-05-24 | FDB5WB | BEY → DXB | May 24, 21:30 UTC | May 25, 15:05 UTC | 17h 35m |
| 2026-05-24 | FDB7KL | AMM → DXB | May 24, 19:50 UTC | May 24, 20:00 UTC | 10m |
| 2026-05-23 | FDB7KL | AMM → DXB | May 23, 21:35 UTC | May 24, 18:20 UTC | 20h 45m |
| 2026-05-23 | FDB7KL | AMM → DXB | May 23, 19:40 UTC | May 24, 18:20 UTC | 22h 40m |
| 2026-05-23 | FDB864 | DMM → DXB | May 23, 12:45 UTC | May 23, 13:40 UTC | 55m |
| 2026-05-23 | FDB9RQ | DOH → DXB | May 23, 07:45 UTC | May 23, 08:05 UTC | 20m |
| 2026-05-22 | FDB1134 | KTM → DXB | May 22, 03:50 UTC | May 22, 22:20 UTC | 18h 30m |
| 2026-05-21 | FDB1133 | DXB → KTM | May 21, 13:10 UTC | May 22, 01:30 UTC | 12h 20m |
| 2026-05-20 | FDB7ZK | DOH → DXB | May 20, 16:35 UTC | May 20, 17:20 UTC | 45m |
| 2026-05-19 | FDB1082 | TLV → DXB | May 19, 15:10 UTC | May 19, 15:40 UTC | 30m |
| 2026-05-19 | FDB1082 | TLV → DXB | May 19, 13:15 UTC | May 19, 13:35 UTC | 20m |
| 2026-05-19 | FDB1081 | DXB → TLV | May 19, 11:35 UTC | May 19, 11:40 UTC | 5m |
| 2026-05-18 | FDB1082 | TLV → DXB | May 18, 14:55 UTC | May 19, 09:20 UTC | 18h 24m |
| 2026-05-18 | FDB1082 | TLV → DXB | May 18, 13:05 UTC | May 18, 13:20 UTC | 15m |
| 2026-05-18 | FDB1081 | DXB → TLV | May 18, 11:20 UTC | May 18, 11:35 UTC | 15m |
| 2026-05-17 | FDB540 | KTM → DXB | May 17, 11:20 UTC | May 18, 01:00 UTC | 13h 40m |
| 2026-05-17 | FDB539 | DXB → KTM | May 17, 07:25 UTC | May 17, 08:15 UTC | 50m |
| 2026-05-16 | FDB59J | BAH → DXB | May 16, 15:45 UTC | May 16, 16:40 UTC | 55m |
| 2026-05-14 | FDB605 | DXB → ADD | May 14, 21:50 UTC | May 14, 22:10 UTC | 20m |
| 2026-05-13 | FDB4DT | DXB → SKT | May 13, 22:40 UTC | May 14, 01:30 UTC | 2h 50m |
| 2026-05-13 | FDB884 | DMM → DXB | May 13, 05:40 UTC | May 13, 06:40 UTC | 1h 0m |
| 2026-05-12 | FDB948 | AQI → DXB | May 12, 10:50 UTC | May 12, 11:35 UTC | 45m |
| 2026-05-11 | FDB64X | - | May 11, 09:25 UTC | May 11, 09:55 UTC | 30m |
| 2026-05-09 | FDB570 | CMB → DXB | May 9, 21:19 UTC | May 10, 10:05 UTC | 12h 45m |
| 2026-05-09 | FDB569 | DXB → CMB | May 9, 17:45 UTC | May 9, 18:45 UTC | 1h 0m |
| 2026-05-08 | FDB3TH | DXB → BAH | May 8, 12:25 UTC | May 8, 12:39 UTC | 15m |
| 2026-05-07 | FDB176 | HBE → DXB | May 7, 21:15 UTC | May 8, 11:34 UTC | 14h 20m |
| 2026-05-07 | FDB580 | CMB → DXB | May 7, 04:30 UTC | May 7, 19:40 UTC | 15h 10m |
| 2026-05-07 | FDB579 | DXB → CMB | May 7, 01:15 UTC | May 7, 02:10 UTC | 55m |
| 2026-05-05 | FDB3YX | DXB → KHI | May 5, 08:55 UTC | May 5, 09:25 UTC | 30m |
| 2026-05-04 | FDB808 | JED → DXB | May 4, 16:40 UTC | May 4, 22:05 UTC | 5h 26m |
| 2026-05-04 | FDB848 | RUH → DXB | May 4, 03:40 UTC | May 4, 08:50 UTC | 5h 10m |
| 2026-05-03 | FDB830 | JED → DXB | May 3, 10:45 UTC | May 3, 17:24 UTC | 6h 40m |
| 2026-05-02 | FDB919 | DXB → JED | May 2, 22:15 UTC | May 3, 04:10 UTC | 5h 54m |
| 2026-05-02 | FDB818 | YNB → DXB | May 2, 10:20 UTC | May 2, 16:35 UTC | 6h 15m |
| 2026-05-01 | FDB920 | JED → DXB | May 1, 22:40 UTC | May 2, 05:25 UTC | 6h 45m |
| 2026-04-30 | FDB9FX | SKT → DXB | Apr 30, 22:45 UTC | May 1, 03:45 UTC | 5h 0m |
| 2026-04-30 | FDB4DT | DXB → SKT | Apr 30, 20:40 UTC | Apr 30, 21:05 UTC | 25m |
| 2026-04-29 | FDB75L | BAH → DXB | Apr 29, 13:00 UTC | Apr 29, 13:50 UTC | 50m |
| 2026-04-29 | FDB15L | DXB → BAH | Apr 29, 10:40 UTC | Apr 29, 11:25 UTC | 45m |
| 2026-04-28 | FDB430 | CCJ → DXB | Apr 28, 03:05 UTC | Apr 28, 06:35 UTC | 3h 30m |
| 2026-04-27 | FDB2JQ | DXB → CCJ | Apr 27, 22:00 UTC | Apr 28, 01:10 UTC | 3h 10m |
| 2026-04-27 | FDB75L | BAH → DXB | Apr 27, 12:50 UTC | Apr 27, 13:45 UTC | 55m |
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-FKC page for operator, model, and routing details .