sensors Mode-S transponder
8964D0
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMA · BOEING 737 MAX 8
- Hex
- 8964D0
- Octal
- 42262320
- Decimal
- 9,004,240
- Country
- AE
- Tail
- A6-FMA
- Type
- B38M
- Flights observed
- 91
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 8964D0 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 |
|---|---|---|---|
| FDB573 | Fly Dubai | 5 | 2026-05-17 |
| FDB4CE | Fly Dubai | 5 | 2026-05-26 |
| FDB989 | Fly Dubai | 4 | 2026-04-17 |
| FDB441 | Fly Dubai | 4 | 2026-05-02 |
| FDB1133 | Fly Dubai | 4 | 2026-05-21 |
| FDB7AF | Fly Dubai | 3 | 2026-05-02 |
| FDB5YA | Fly Dubai | 3 | 2026-04-17 |
| FDB574 | Fly Dubai | 3 | 2026-05-17 |
| FDB2DC | Fly Dubai | 3 | 2026-04-28 |
| FDB1549 | Fly Dubai | 3 | 2026-05-26 |
| FDB14Q | Fly Dubai | 3 | 2026-05-26 |
| FDB1134 | Fly Dubai | 3 | 2026-05-21 |
| FDB7UE | Fly Dubai | 2 | 2026-04-14 |
| FDB65E | Fly Dubai | 2 | 2026-05-01 |
| FDB580 | Fly Dubai | 2 | 2026-05-04 |
| FDB3CF | Fly Dubai | 2 | 2026-05-24 |
| FDB1596 | Fly Dubai | 2 | 2026-04-19 |
| FDB1126 | Fly Dubai | 2 | 2026-05-08 |
| FDB9DV | Fly Dubai | 1 | 2026-04-26 |
| FDB93Q | Fly Dubai | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB4TA | ZAG → DXB | May 29, 13:50 UTC | May 29, 16:25 UTC | 2h 35m |
| 2026-05-29 | FDB4MA | DXB → ZAG | May 29, 10:10 UTC | May 29, 12:15 UTC | 2h 5m |
| 2026-05-26 | FDB4CE | BEG → DXB | May 26, 21:49 UTC | May 27, 00:34 UTC | 2h 45m |
| 2026-05-26 | FDB14Q | DXB → BEG | May 26, 08:30 UTC | May 26, 20:09 UTC | 11h 40m |
| 2026-05-26 | FDB1549 | DXB → TLV | May 26, 06:39 UTC | May 26, 06:54 UTC | 15m |
| 2026-05-24 | FDB1QS | PRG → DXB | May 24, 19:35 UTC | May 24, 23:15 UTC | 3h 40m |
| 2026-05-24 | FDB3CF | DXB → PRG | May 24, 15:25 UTC | May 24, 17:25 UTC | 2h 0m |
| 2026-05-23 | FDB3CF | DXB → PRG | May 23, 16:10 UTC | May 24, 16:00 UTC | 23h 50m |
| 2026-05-23 | FDB93Q | NAP → DXB | May 23, 11:35 UTC | May 23, 16:40 UTC | 5h 5m |
| 2026-05-22 | FDB3UM | DXB → NAP | May 22, 19:00 UTC | May 23, 10:10 UTC | 15h 9m |
| 2026-05-21 | FDB4CE | BEG → DXB | May 21, 22:15 UTC | May 22, 03:15 UTC | 5h 0m |
| 2026-05-21 | FDB1134 | KTM → DXB | May 21, 04:25 UTC | May 21, 20:30 UTC | 16h 5m |
| 2026-05-21 | FDB1133 | DXB → KTM | May 21, 00:20 UTC | May 21, 02:05 UTC | 1h 45m |
| 2026-05-19 | FDB1134 | KTM → DXB | May 19, 03:50 UTC | May 19, 20:25 UTC | 16h 35m |
| 2026-05-18 | FDB1133 | DXB → KTM | May 18, 12:40 UTC | May 19, 01:25 UTC | 12h 44m |
| 2026-05-17 | FDB574 | KTM → DXB | May 17, 17:55 UTC | May 18, 07:25 UTC | 13h 30m |
| 2026-05-17 | FDB573 | DXB → KTM | May 17, 14:05 UTC | May 17, 15:01 UTC | 55m |
| 2026-05-16 | FDB573 | DXB → KTM | May 16, 18:55 UTC | May 17, 15:01 UTC | 20h 5m |
| 2026-05-16 | FDB574 | KTM → DXB | May 16, 17:05 UTC | May 17, 15:01 UTC | 21h 55m |
| 2026-05-16 | FDB573 | DXB → KTM | May 16, 14:11 UTC | May 16, 15:35 UTC | 1h 25m |
| 2026-05-14 | FDB2FL | DXB → BGW | May 14, 12:35 UTC | May 15, 06:30 UTC | 17h 55m |
| 2026-05-13 | FDB574 | KTM → DXB | May 13, 17:55 UTC | May 13, 20:35 UTC | 2h 40m |
| 2026-05-13 | FDB573 | DXB → KTM | May 13, 14:05 UTC | May 13, 15:35 UTC | 1h 30m |
| 2026-05-13 | FDB573 | DXB → KTM | May 13, 12:05 UTC | May 13, 12:20 UTC | 15m |
| 2026-05-13 | FDB4CE | BEG → DXB | May 13, 01:10 UTC | May 13, 02:25 UTC | 1h 15m |
| 2026-05-12 | FDB4CE | BEG → DXB | May 12, 23:55 UTC | May 13, 01:05 UTC | 1h 10m |
| 2026-05-12 | FDB14Q | DXB → BEG | May 12, 11:35 UTC | May 12, 22:40 UTC | 11h 5m |
| 2026-05-11 | FDB1134 | KTM → DXB | May 11, 04:35 UTC | May 11, 07:15 UTC | 2h 40m |
| 2026-05-11 | FDB1133 | DXB → KTM | May 11, 01:50 UTC | May 11, 02:55 UTC | 1h 5m |
| 2026-05-10 | FDB1133 | DXB → KTM | May 10, 09:20 UTC | May 11, 01:20 UTC | 16h 0m |
| 2026-05-09 | FDB4RM | DXB → SPX | May 9, 17:35 UTC | May 10, 09:30 UTC | 15h 55m |
| 2026-05-08 | FDB1126 | TLV → DXB | May 8, 17:10 UTC | May 8, 17:50 UTC | 40m |
| 2026-05-08 | FDB1126 | TLV → DXB | May 8, 15:10 UTC | May 8, 15:30 UTC | 20m |
| 2026-05-06 | FDB71T | TBS → DXB | May 6, 13:05 UTC | May 6, 17:10 UTC | 4h 5m |
| 2026-05-06 | FDB2WK | DXB → TBS | May 6, 11:05 UTC | May 6, 11:30 UTC | 25m |
| 2026-05-04 | FDB580 | CMB → DXB | May 4, 15:20 UTC | May 5, 08:00 UTC | 16h 41m |
| 2026-05-04 | FDB580 | CMB → DXB | May 4, 08:20 UTC | May 5, 08:00 UTC | 23h 41m |
| 2026-05-04 | FDB732 | ASB → DXB | May 4, 03:40 UTC | May 4, 04:00 UTC | 20m |
| 2026-05-03 | FDB731 | DXB → ASB | May 3, 19:05 UTC | May 3, 19:20 UTC | 15m |
| 2026-05-03 | FDB3DK | EBL → DXB | May 3, 07:05 UTC | May 3, 15:25 UTC | 8h 20m |
| 2026-05-02 | FDB7AF | DEL → DXB | May 2, 22:55 UTC | May 3, 02:10 UTC | 3h 15m |
| 2026-05-02 | FDB441 | DXB → DEL | May 2, 20:45 UTC | May 2, 21:25 UTC | 40m |
| 2026-05-02 | FDB7XZ | BGW → DXB | May 2, 06:10 UTC | May 2, 14:10 UTC | 8h 0m |
| 2026-05-01 | FDB65E | EBB → DXB | May 1, 10:25 UTC | May 1, 21:50 UTC | 11h 25m |
| 2026-04-30 | FDB646 | ASM → DXB | Apr 30, 15:30 UTC | Apr 30, 23:30 UTC | 8h 0m |
| 2026-04-30 | FDB913 | DXB → AJF | Apr 30, 05:25 UTC | Apr 30, 12:05 UTC | 6h 40m |
| 2026-04-29 | FDB645 | DXB → ASM | Apr 29, 15:25 UTC | Apr 29, 16:35 UTC | 1h 10m |
| 2026-04-29 | FDB1550 | TLV → DXB | Apr 29, 08:55 UTC | Apr 29, 12:05 UTC | 3h 11m |
| 2026-04-29 | FDB1549 | DXB → TLV | Apr 29, 06:59 UTC | Apr 29, 07:20 UTC | 20m |
| 2026-04-29 | FDB1549 | DXB → TLV | Apr 29, 03:40 UTC | Apr 29, 04:44 UTC | 1h 5m |
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-FMA page for operator, model, and routing details .