sensors Mode-S transponder
8965B5
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMY · BOEING 737 MAX 8
- Hex
- 8965B5
- Octal
- 42262665
- Decimal
- 9,004,469
- Country
- AE
- Tail
- A6-FMY
- Type
- B38M
- Flights observed
- 105
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 8965B5 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 |
|---|---|---|---|
| FDB5GE | Fly Dubai | 5 | 2026-05-07 |
| FDB573 | Fly Dubai | 5 | 2026-05-19 |
| FDB4TA | - | 5 | 2026-04-13 |
| FDB443 | Fly Dubai | 5 | 2026-05-01 |
| FDB2RG | Fly Dubai | 5 | 2026-05-25 |
| FDB3PL | Fly Dubai | 4 | 2026-05-24 |
| FDB1BH | Fly Dubai | 4 | 2026-05-22 |
| FDB868 | Fly Dubai | 3 | 2026-05-12 |
| FDB574 | Fly Dubai | 3 | 2026-05-19 |
| FDB444 | Fly Dubai | 3 | 2026-05-02 |
| FDB354 | Fly Dubai | 3 | 2026-04-29 |
| FDB353 | Fly Dubai | 3 | 2026-04-28 |
| FDB1NU | Fly Dubai | 3 | 2026-05-07 |
| FDB1688 | Fly Dubai | 3 | 2026-05-10 |
| FDB9JZ | Fly Dubai | 2 | 2026-05-04 |
| FDB989 | Fly Dubai | 2 | 2026-05-24 |
| FDB867 | Fly Dubai | 2 | 2026-05-12 |
| FDB7UE | Fly Dubai | 2 | 2026-05-16 |
| FDB7ML | Fly Dubai | 2 | 2026-05-13 |
| FDB7KL | Fly Dubai | 2 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1502 | CTA → DXB | May 29, 11:35 UTC | May 29, 16:15 UTC | 4h 40m |
| 2026-05-29 | FDB5HR | DXB → CTA | May 29, 05:55 UTC | May 29, 08:50 UTC | 2h 55m |
| 2026-05-26 | FDB454 | COK → DXB | May 26, 21:49 UTC | May 26, 23:19 UTC | 1h 30m |
| 2026-05-26 | FDB7XZ | BGW → DXB | May 26, 12:00 UTC | May 26, 20:15 UTC | 8h 15m |
| 2026-05-25 | FDB2RG | OTP → DXB | May 25, 17:30 UTC | May 26, 12:40 UTC | 19h 9m |
| 2026-05-25 | FDB2RG | OTP → DXB | May 25, 15:55 UTC | May 26, 12:40 UTC | 20h 44m |
| 2026-05-25 | FDB2RG | OTP → DXB | May 25, 13:45 UTC | May 26, 12:40 UTC | 22h 55m |
| 2026-05-24 | FDB3PL | DXB → OTP | May 24, 20:05 UTC | May 25, 12:20 UTC | 16h 15m |
| 2026-05-24 | FDB989 | DXB → VKO | May 24, 07:15 UTC | May 24, 20:05 UTC | 12h 50m |
| 2026-05-23 | FDB989 | DXB → VKO | May 23, 05:25 UTC | May 23, 05:35 UTC | 10m |
| 2026-05-22 | FDB1BH | TBS → DXB | May 22, 08:55 UTC | May 22, 23:40 UTC | 14h 45m |
| 2026-05-21 | FDB4XN | DXB → TBS | May 21, 11:50 UTC | May 22, 06:45 UTC | 18h 55m |
| 2026-05-21 | FDB1BH | TBS → DXB | May 21, 09:20 UTC | May 22, 06:45 UTC | 21h 25m |
| 2026-05-21 | FDB1BH | TBS → DXB | May 21, 09:00 UTC | May 22, 06:45 UTC | 21h 45m |
| 2026-05-20 | FDB1BM | - | May 20, 12:55 UTC | May 21, 06:30 UTC | 17h 35m |
| 2026-05-19 | FDB574 | KTM → DXB | May 19, 18:50 UTC | May 20, 11:10 UTC | 16h 21m |
| 2026-05-19 | FDB573 | DXB → KTM | May 19, 17:15 UTC | May 19, 17:25 UTC | 10m |
| 2026-05-19 | FDB573 | DXB → KTM | May 19, 15:40 UTC | May 19, 16:35 UTC | 55m |
| 2026-05-17 | FDB71T | TBS → DXB | May 17, 12:55 UTC | May 17, 13:25 UTC | 30m |
| 2026-05-17 | FDB2WK | DXB → TBS | May 17, 01:20 UTC | May 17, 10:55 UTC | 9h 35m |
| 2026-05-16 | FDB1941 | DXB → TAS | May 16, 18:05 UTC | May 16, 18:25 UTC | 20m |
| 2026-05-16 | FDB7UE | EVN → DXB | May 16, 11:31 UTC | May 16, 12:11 UTC | 40m |
| 2026-05-15 | FDB1126 | TLV → DXB | May 15, 17:35 UTC | May 16, 07:16 UTC | 13h 41m |
| 2026-05-15 | FDB1126 | TLV → DXB | May 15, 15:30 UTC | May 15, 15:45 UTC | 15m |
| 2026-05-15 | FDB1125 | DXB → TLV | May 15, 13:35 UTC | May 15, 14:00 UTC | 25m |
| 2026-05-14 | FDB7KL | AMM → DXB | May 14, 21:30 UTC | May 15, 11:40 UTC | 14h 10m |
| 2026-05-14 | FDB7KL | AMM → DXB | May 14, 00:35 UTC | May 14, 22:05 UTC | 21h 30m |
| 2026-05-13 | FDB7ML | RMO → DXB | May 13, 14:00 UTC | May 13, 16:10 UTC | 2h 10m |
| 2026-05-12 | FDB868 | DMM → DXB | May 12, 17:20 UTC | May 13, 16:10 UTC | 22h 50m |
| 2026-05-12 | FDB868 | DMM → DXB | May 12, 17:10 UTC | May 13, 14:15 UTC | 21h 5m |
| 2026-05-12 | FDB867 | DXB → DMM | May 12, 15:20 UTC | May 12, 15:40 UTC | 20m |
| 2026-05-11 | FDB913 | DXB → AJF | May 11, 04:45 UTC | May 11, 20:40 UTC | 15h 56m |
| 2026-05-10 | FDB1688 | ZNZ → DXB | May 10, 22:45 UTC | May 10, 23:15 UTC | 30m |
| 2026-05-09 | FDB1688 | ZNZ → DXB | May 9, 23:20 UTC | May 10, 23:15 UTC | 23h 55m |
| 2026-05-09 | FDB7AF | DEL → DXB | May 9, 23:05 UTC | May 9, 23:44 UTC | 40m |
| 2026-05-09 | FDB441 | DXB → DEL | May 9, 20:49 UTC | May 9, 21:30 UTC | 40m |
| 2026-05-09 | FDB441 | DXB → DEL | May 9, 18:35 UTC | May 9, 18:50 UTC | 15m |
| 2026-05-09 | FDB1BH | TBS → DXB | May 9, 08:45 UTC | May 9, 12:50 UTC | 4h 5m |
| 2026-05-09 | FDB4XN | DXB → TBS | May 9, 06:15 UTC | May 9, 06:50 UTC | 35m |
| 2026-05-08 | FDB707 | DXB → GYD | May 8, 10:54 UTC | May 8, 11:34 UTC | 40m |
| 2026-05-07 | FDB5GE | OTP → DXB | May 7, 06:55 UTC | May 7, 11:15 UTC | 4h 20m |
| 2026-05-07 | FDB1NU | DXB → OTP | May 7, 02:45 UTC | May 7, 05:15 UTC | 2h 30m |
| 2026-05-04 | FDB9JZ | GYD → DXB | May 4, 00:50 UTC | May 4, 01:20 UTC | 30m |
| 2026-05-03 | FDB733 | DXB → GYD | May 3, 11:55 UTC | May 3, 12:15 UTC | 20m |
| 2026-05-03 | FDB580 | CMB → DXB | May 3, 00:20 UTC | May 3, 08:20 UTC | 7h 59m |
| 2026-05-02 | FDB444 | LKO → DXB | May 2, 02:40 UTC | May 2, 06:15 UTC | 3h 35m |
| 2026-05-01 | FDB443 | DXB → LKO | May 1, 23:55 UTC | May 2, 01:00 UTC | 1h 5m |
| 2026-05-01 | FDB443 | DXB → LKO | May 1, 21:50 UTC | May 1, 22:15 UTC | 25m |
| 2026-05-01 | FDB2RG | OTP → DXB | May 1, 12:15 UTC | May 1, 17:15 UTC | 5h 0m |
| 2026-05-01 | FDB3PL | DXB → OTP | May 1, 04:55 UTC | May 1, 10:30 UTC | 5h 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-FMY page for operator, model, and routing details .