sensors Mode-S transponder
8965B6
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMZ · BOEING 737 MAX 8
- Hex
- 8965B6
- Octal
- 42262666
- Decimal
- 9,004,470
- Country
- AE
- Tail
- A6-FMZ
- Type
- B38M
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 8965B6 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 |
|---|---|---|---|
| FDB52X | Fly Dubai | 6 | 2026-06-03 |
| FDB443 | Fly Dubai | 4 | 2026-05-22 |
| FDB1BM | - | 4 | 2026-06-03 |
| FDB1212 | Fly Dubai | 4 | 2026-05-13 |
| FDB7ML | Fly Dubai | 3 | 2026-05-27 |
| FDB441 | Fly Dubai | 3 | 2026-05-12 |
| FDB3DK | Fly Dubai | 3 | 2026-05-13 |
| FDB1134 | Fly Dubai | 3 | 2026-06-06 |
| FDB1133 | Fly Dubai | 3 | 2026-05-24 |
| FDB872 | - | 2 | 2026-05-08 |
| FDB7AF | Fly Dubai | 2 | 2026-05-12 |
| FDB71T | Fly Dubai | 2 | 2026-05-18 |
| FDB707 | Fly Dubai | 2 | 2026-05-26 |
| FDB445 | Fly Dubai | 2 | 2026-05-21 |
| FDB2WK | Fly Dubai | 2 | 2026-05-18 |
| FDB2MF | Fly Dubai | 2 | 2026-05-24 |
| FDB23L | Fly Dubai | 2 | 2026-05-29 |
| FDB9RF | Fly Dubai | 1 | 2026-05-17 |
| FDB9007 | - | 1 | 2026-04-20 |
| FDB871 | - | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | FDB1134 | KTM → DXB | Jun 6, 03:50 UTC | Jun 6, 04:35 UTC | 45m |
| 2026-06-05 | FDB4TA | ZAG → DXB | Jun 5, 13:25 UTC | Jun 6, 02:10 UTC | 12h 45m |
| 2026-06-05 | FDB4MA | DXB → ZAG | Jun 5, 09:55 UTC | Jun 5, 11:55 UTC | 2h 0m |
| 2026-06-04 | FDB1134 | KTM → DXB | Jun 4, 03:40 UTC | Jun 4, 05:05 UTC | 1h 25m |
| 2026-06-03 | FDB1BM | - | Jun 3, 12:55 UTC | Jun 4, 02:10 UTC | 13h 15m |
| 2026-06-03 | FDB52X | DXB → SJJ | Jun 3, 05:45 UTC | Jun 3, 10:10 UTC | 4h 25m |
| 2026-05-30 | FDB750 | TIV → DXB | May 30, 16:30 UTC | May 30, 21:20 UTC | 4h 50m |
| 2026-05-30 | FDB749 | DXB → TIV | May 30, 09:50 UTC | May 30, 14:35 UTC | 4h 45m |
| 2026-05-29 | FDB23L | DXB → GYD | May 29, 05:15 UTC | May 29, 05:45 UTC | 30m |
| 2026-05-28 | FDB23L | DXB → GYD | May 28, 08:40 UTC | May 29, 05:45 UTC | 21h 5m |
| 2026-05-27 | FDB7ML | RMO → DXB | May 27, 14:05 UTC | May 28, 08:55 UTC | 18h 50m |
| 2026-05-27 | FDB7ML | RMO → DXB | May 27, 12:05 UTC | May 28, 08:55 UTC | 20h 50m |
| 2026-05-27 | FDB7ML | RMO → DXB | May 27, 07:05 UTC | May 27, 16:30 UTC | 9h 25m |
| 2026-05-26 | FDB37M | DXB → RMO | May 26, 11:34 UTC | May 27, 09:20 UTC | 21h 45m |
| 2026-05-26 | FDB707 | DXB → GYD | May 26, 11:20 UTC | May 27, 09:20 UTC | 22h 0m |
| 2026-05-24 | FDB2MF | IST → DXB | May 24, 16:55 UTC | May 24, 21:00 UTC | 4h 5m |
| 2026-05-24 | FDB1134 | KTM → DXB | May 24, 04:00 UTC | May 24, 06:45 UTC | 2h 45m |
| 2026-05-24 | FDB1133 | DXB → KTM | May 24, 00:20 UTC | May 24, 01:45 UTC | 1h 25m |
| 2026-05-23 | FDB1133 | DXB → KTM | May 23, 03:35 UTC | May 24, 01:45 UTC | 22h 11m |
| 2026-05-23 | FDB1133 | DXB → KTM | May 23, 03:25 UTC | May 24, 01:30 UTC | 22h 6m |
| 2026-05-22 | FDB443 | DXB → LKO | May 22, 11:45 UTC | May 23, 01:05 UTC | 13h 20m |
| 2026-05-22 | FDB443 | DXB → LKO | May 22, 01:35 UTC | May 23, 01:05 UTC | 23h 30m |
| 2026-05-22 | FDB707 | DXB → GYD | May 22, 01:05 UTC | May 22, 12:25 UTC | 11h 20m |
| 2026-05-21 | FDB445 | DXB → BOM | May 21, 22:15 UTC | May 21, 23:15 UTC | 1h 0m |
| 2026-05-20 | FDB435 | DXB → HYD | May 20, 18:35 UTC | May 20, 23:00 UTC | 4h 25m |
| 2026-05-18 | FDB71T | TBS → DXB | May 18, 12:30 UTC | May 18, 16:05 UTC | 3h 35m |
| 2026-05-18 | FDB2WK | DXB → TBS | May 18, 07:35 UTC | May 18, 10:35 UTC | 3h 0m |
| 2026-05-17 | FDB454 | COK → DXB | May 17, 21:45 UTC | May 17, 23:10 UTC | 1h 25m |
| 2026-05-17 | FDB9RF | DXB → COK | May 17, 18:25 UTC | May 17, 20:01 UTC | 1h 35m |
| 2026-05-16 | FDB1BM | - | May 16, 12:25 UTC | May 16, 16:40 UTC | 4h 15m |
| 2026-05-16 | FDB52X | DXB → SJJ | May 16, 04:55 UTC | May 16, 10:46 UTC | 5h 51m |
| 2026-05-15 | FDB619 | DXB → EBB | May 15, 01:20 UTC | May 15, 01:35 UTC | 15m |
| 2026-05-13 | FDB3DK | EBL → DXB | May 13, 20:35 UTC | May 14, 14:30 UTC | 17h 55m |
| 2026-05-13 | FDB1212 | TLV → DXB | May 13, 12:40 UTC | May 14, 02:05 UTC | 13h 25m |
| 2026-05-13 | FDB1212 | TLV → DXB | May 13, 10:45 UTC | May 13, 11:00 UTC | 15m |
| 2026-05-12 | FDB7AF | DEL → DXB | May 12, 23:40 UTC | May 13, 06:40 UTC | 7h 0m |
| 2026-05-12 | FDB441 | DXB → DEL | May 12, 21:20 UTC | May 12, 22:01 UTC | 40m |
| 2026-05-11 | FDB7UE | EVN → DXB | May 11, 15:35 UTC | May 11, 20:35 UTC | 5h 1m |
| 2026-05-10 | FDB746 | TIA → DXB | May 10, 11:30 UTC | May 10, 16:44 UTC | 5h 15m |
| 2026-05-09 | FDB34Q | DXB → TIA | May 9, 14:00 UTC | May 10, 09:15 UTC | 19h 15m |
| 2026-05-09 | FDB3DK | EBL → DXB | May 9, 07:55 UTC | May 10, 07:30 UTC | 23h 35m |
| 2026-05-08 | FDB872 | - | May 8, 22:45 UTC | May 9, 14:30 UTC | 15h 45m |
| 2026-05-08 | FDB872 | - | May 8, 13:35 UTC | May 9, 08:10 UTC | 18h 35m |
| 2026-05-08 | FDB1212 | TLV → DXB | May 8, 13:00 UTC | May 9, 08:10 UTC | 19h 10m |
| 2026-05-08 | FDB1212 | TLV → DXB | May 8, 11:05 UTC | May 9, 08:10 UTC | 21h 5m |
| 2026-05-08 | FDB1211 | DXB → TLV | May 8, 09:04 UTC | May 8, 09:34 UTC | 30m |
| 2026-05-07 | FDB2MF | IST → DXB | May 7, 18:40 UTC | May 7, 20:55 UTC | 2h 15m |
| 2026-05-06 | FDB1BM | - | May 6, 13:10 UTC | May 6, 17:55 UTC | 4h 44m |
| 2026-05-05 | FDB52X | DXB → SJJ | May 5, 17:35 UTC | May 6, 11:50 UTC | 18h 15m |
| 2026-05-05 | FDB52X | DXB → SJJ | May 5, 17:05 UTC | May 6, 11:50 UTC | 18h 45m |
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-FMZ page for operator, model, and routing details .