sensors Mode-S transponder
8965D3
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKH · BOEING 737 MAX 8
- Hex
- 8965D3
- Octal
- 42262723
- Decimal
- 9,004,499
- Country
- AE
- Tail
- A6-FKH
- Type
- B38M
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 8965D3 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 |
|---|---|---|---|
| FDB5DN | Fly Dubai | 3 | 2026-05-12 |
| FDB1808 | Fly Dubai | 3 | 2026-05-28 |
| FDB882 | Fly Dubai | 2 | 2026-05-13 |
| FDB7KL | Fly Dubai | 2 | 2026-05-08 |
| FDB570 | Fly Dubai | 2 | 2026-05-10 |
| FDB569 | Fly Dubai | 2 | 2026-05-10 |
| FDB4JZ | Fly Dubai | 2 | 2026-04-18 |
| FDB4GP | Fly Dubai | 2 | 2026-05-31 |
| FDB430 | Fly Dubai | 2 | 2026-04-26 |
| FDB3TH | Fly Dubai | 2 | 2026-04-21 |
| FDB2PE | Fly Dubai | 2 | 2026-05-23 |
| FDB2JQ | Fly Dubai | 2 | 2026-04-25 |
| FDB1YT | Fly Dubai | 2 | 2026-04-18 |
| FDB175 | Fly Dubai | 2 | 2026-05-24 |
| FDB1636 | Fly Dubai | 2 | 2026-06-01 |
| FDB15L | Fly Dubai | 2 | 2026-04-22 |
| FDB9RF | Fly Dubai | 1 | 2026-04-26 |
| FDB9QG | Fly Dubai | 1 | 2026-04-15 |
| FDB920 | Fly Dubai | 1 | 2026-05-09 |
| FDB915 | Fly Dubai | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FDB811 | DXB → AHB | Jun 2, 05:15 UTC | Jun 2, 13:05 UTC | 7h 50m |
| 2026-06-01 | FDB1636 | TLV → DXB | Jun 1, 15:55 UTC | Jun 2, 13:05 UTC | 21h 10m |
| 2026-06-01 | FDB1636 | TLV → DXB | Jun 1, 14:10 UTC | Jun 2, 05:20 UTC | 15h 10m |
| 2026-05-31 | FDB2MF | IST → DXB | May 31, 17:00 UTC | May 31, 20:45 UTC | 3h 45m |
| 2026-05-31 | FDB4GP | DXB → IST | May 31, 00:30 UTC | May 31, 15:05 UTC | 14h 35m |
| 2026-05-30 | FDB4GP | DXB → IST | May 30, 17:25 UTC | May 31, 15:05 UTC | 21h 40m |
| 2026-05-29 | FDB830 | JED → DXB | May 29, 16:10 UTC | May 29, 16:45 UTC | 35m |
| 2026-05-28 | FDB1808 | TLV → DXB | May 28, 19:55 UTC | May 29, 16:45 UTC | 20h 51m |
| 2026-05-26 | FDB3CK | AMM → DXB | May 26, 09:09 UTC | May 27, 03:20 UTC | 18h 10m |
| 2026-05-25 | FDB1808 | TLV → DXB | May 25, 19:59 UTC | May 26, 06:04 UTC | 10h 5m |
| 2026-05-25 | FDB1808 | TLV → DXB | May 25, 18:10 UTC | May 25, 18:30 UTC | 20m |
| 2026-05-25 | FDB1807 | DXB → TLV | May 25, 16:00 UTC | May 25, 16:25 UTC | 25m |
| 2026-05-24 | FDB176 | HBE → DXB | May 24, 21:25 UTC | May 24, 21:45 UTC | 20m |
| 2026-05-24 | FDB175 | DXB → HBE | May 24, 03:20 UTC | May 24, 19:45 UTC | 16h 25m |
| 2026-05-23 | FDB175 | DXB → HBE | May 23, 22:50 UTC | May 24, 19:45 UTC | 20h 55m |
| 2026-05-23 | FDB2PE | BEY → DXB | May 23, 15:45 UTC | May 24, 04:00 UTC | 12h 16m |
| 2026-05-22 | FDB184 | HBE → DXB | May 22, 18:05 UTC | May 22, 21:10 UTC | 3h 5m |
| 2026-05-22 | FDB580 | CMB → DXB | May 22, 04:35 UTC | May 22, 16:50 UTC | 12h 15m |
| 2026-05-22 | FDB579 | DXB → CMB | May 22, 00:10 UTC | May 22, 02:05 UTC | 1h 55m |
| 2026-05-20 | FDB1116 | DAM → DXB | May 20, 08:35 UTC | May 20, 10:45 UTC | 2h 10m |
| 2026-05-19 | FDB2PE | BEY → DXB | May 19, 13:25 UTC | May 20, 06:50 UTC | 17h 26m |
| 2026-05-17 | FDB3JE | MRV → DXB | May 17, 17:01 UTC | May 18, 02:40 UTC | 9h 40m |
| 2026-05-16 | FDB5PG | DXB → MRV | May 16, 17:50 UTC | May 16, 22:35 UTC | 4h 45m |
| 2026-05-13 | FDB882 | TUU → DXB | May 13, 12:00 UTC | May 13, 18:05 UTC | 6h 5m |
| 2026-05-12 | FDB5DN | ISU → DXB | May 12, 13:00 UTC | May 13, 12:05 UTC | 23h 5m |
| 2026-05-11 | FDB5DN | ISU → DXB | May 11, 16:50 UTC | May 12, 13:40 UTC | 20h 51m |
| 2026-05-11 | FDB5DN | ISU → DXB | May 11, 16:40 UTC | May 12, 13:40 UTC | 21h 1m |
| 2026-05-10 | FDB570 | CMB → DXB | May 10, 21:14 UTC | May 11, 17:10 UTC | 19h 56m |
| 2026-05-10 | FDB569 | DXB → CMB | May 10, 03:25 UTC | May 10, 18:49 UTC | 15h 25m |
| 2026-05-09 | FDB920 | JED → DXB | May 9, 09:15 UTC | May 10, 04:00 UTC | 18h 45m |
| 2026-05-08 | FDB7KL | AMM → DXB | May 8, 19:35 UTC | May 9, 09:20 UTC | 13h 45m |
| 2026-05-06 | FDB7KL | AMM → DXB | May 6, 15:40 UTC | May 6, 22:00 UTC | 6h 19m |
| 2026-05-05 | FDB570 | CMB → DXB | May 5, 21:05 UTC | May 6, 17:40 UTC | 20h 34m |
| 2026-05-05 | FDB569 | DXB → CMB | May 5, 17:50 UTC | May 5, 18:50 UTC | 1h 0m |
| 2026-05-05 | FDB312 | KBL → DXB | May 5, 06:15 UTC | May 5, 08:40 UTC | 2h 25m |
| 2026-05-04 | FDB1596 | KTM → DXB | May 4, 15:20 UTC | May 4, 16:25 UTC | 1h 5m |
| 2026-05-04 | FDB1595 | DXB → KTM | May 4, 09:05 UTC | May 4, 12:45 UTC | 3h 40m |
| 2026-05-03 | FDB882 | TUU → DXB | May 3, 10:55 UTC | May 3, 18:09 UTC | 7h 15m |
| 2026-05-03 | FDB606 | ADD → DXB | May 3, 06:45 UTC | May 3, 07:00 UTC | 15m |
| 2026-05-02 | FDB308 | KBL → DXB | May 2, 07:55 UTC | May 2, 15:40 UTC | 7h 45m |
| 2026-05-01 | FDB827 | DXB → MED | May 1, 17:45 UTC | May 1, 23:50 UTC | 6h 5m |
| 2026-05-01 | FDB8588 | - | May 1, 03:55 UTC | May 1, 04:25 UTC | 30m |
| 2026-05-01 | FDB8587 | - | May 1, 01:55 UTC | May 1, 02:20 UTC | 25m |
| 2026-04-29 | FDB7WA | MCT → DXB | Apr 29, 17:35 UTC | Apr 29, 18:05 UTC | 30m |
| 2026-04-29 | FDB3PM | DXB → MCT | Apr 29, 14:55 UTC | Apr 29, 15:20 UTC | 25m |
| 2026-04-28 | FDB915 | DXB → EAM | Apr 28, 08:30 UTC | Apr 28, 14:45 UTC | 6h 15m |
| 2026-04-26 | FDB454 | COK → DXB | Apr 26, 22:05 UTC | Apr 27, 01:35 UTC | 3h 30m |
| 2026-04-26 | FDB9RF | DXB → COK | Apr 26, 16:35 UTC | Apr 26, 20:05 UTC | 3h 30m |
| 2026-04-26 | FDB430 | CCJ → DXB | Apr 26, 06:00 UTC | Apr 26, 06:40 UTC | 40m |
| 2026-04-25 | FDB2JQ | DXB → CCJ | Apr 25, 22:05 UTC | Apr 25, 22:40 UTC | 35m |
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-FKH page for operator, model, and routing details .