sensors Mode-S transponder
8964D2
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMC · BOEING 737 MAX 8
- Hex
- 8964D2
- Octal
- 42262322
- Decimal
- 9,004,242
- Country
- AE
- Tail
- A6-FMC
- Type
- B38M
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 8964D2 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 | 4 | 2026-04-22 |
| FDB2RG | Fly Dubai | 4 | 2026-05-23 |
| FDB1134 | - | 4 | 2026-04-13 |
| FDB9YD | Fly Dubai | 3 | 2026-05-29 |
| FDB3PR | Fly Dubai | 3 | 2026-05-22 |
| FDB3HP | Fly Dubai | 3 | 2026-04-29 |
| FDB1NU | Fly Dubai | 3 | 2026-04-22 |
| FDB883 | Fly Dubai | 2 | 2026-04-19 |
| FDB868 | Fly Dubai | 2 | 2026-05-04 |
| FDB867 | Fly Dubai | 2 | 2026-05-04 |
| FDB7AF | Fly Dubai | 2 | 2026-05-15 |
| FDB733 | Fly Dubai | 2 | 2026-05-14 |
| FDB732 | Fly Dubai | 2 | 2026-05-02 |
| FDB731 | Fly Dubai | 2 | 2026-05-01 |
| FDB4GP | Fly Dubai | 2 | 2026-05-13 |
| FDB441 | Fly Dubai | 2 | 2026-05-15 |
| FDB3VG | Fly Dubai | 2 | 2026-04-17 |
| FDB3PL | Fly Dubai | 2 | 2026-04-15 |
| FDB1KS | Fly Dubai | 2 | 2026-05-29 |
| FDB176 | Fly Dubai | 2 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1KS | BEG → DXB | May 29, 13:40 UTC | May 29, 18:15 UTC | 4h 35m |
| 2026-05-29 | FDB9YD | DXB → BEG | May 29, 10:05 UTC | May 29, 11:35 UTC | 1h 30m |
| 2026-05-28 | FDB9YD | DXB → BEG | May 28, 14:35 UTC | May 29, 11:35 UTC | 21h 0m |
| 2026-05-28 | FDB4CW | LJU → DXB | May 28, 12:45 UTC | May 29, 11:35 UTC | 22h 50m |
| 2026-05-27 | FDB3NC | DXB → LJU | May 27, 10:30 UTC | May 27, 10:50 UTC | 20m |
| 2026-05-25 | FDB1550 | TLV → DXB | May 25, 08:35 UTC | May 25, 08:50 UTC | 15m |
| 2026-05-25 | FDB1549 | DXB → TLV | May 25, 06:45 UTC | May 25, 07:05 UTC | 20m |
| 2026-05-24 | FDB1KS | BEG → DXB | May 24, 12:15 UTC | May 24, 17:10 UTC | 4h 55m |
| 2026-05-24 | FDB9YD | DXB → BEG | May 24, 00:10 UTC | May 24, 10:35 UTC | 10h 25m |
| 2026-05-23 | FDB2RG | OTP → DXB | May 23, 12:15 UTC | May 23, 22:40 UTC | 10h 26m |
| 2026-05-22 | FDB3PR | SOF → DXB | May 22, 16:40 UTC | May 23, 10:35 UTC | 17h 54m |
| 2026-05-22 | FDB3PR | SOF → DXB | May 22, 14:35 UTC | May 23, 10:35 UTC | 20h 0m |
| 2026-05-22 | FDB3PR | SOF → DXB | May 22, 13:50 UTC | May 23, 10:35 UTC | 20h 44m |
| 2026-05-22 | FDB5WH | DXB → SOF | May 22, 10:15 UTC | May 22, 10:55 UTC | 40m |
| 2026-05-18 | FDB807 | DXB → JED | May 18, 16:35 UTC | May 19, 15:45 UTC | 23h 9m |
| 2026-05-18 | FDB64X | - | May 18, 09:50 UTC | May 18, 10:40 UTC | 50m |
| 2026-05-15 | FDB7AF | DEL → DXB | May 15, 23:05 UTC | May 15, 23:40 UTC | 35m |
| 2026-05-15 | FDB441 | DXB → DEL | May 15, 20:15 UTC | May 15, 21:25 UTC | 1h 10m |
| 2026-05-14 | FDB733 | DXB → GYD | May 14, 05:00 UTC | May 14, 16:25 UTC | 11h 25m |
| 2026-05-13 | FDB4GP | DXB → IST | May 13, 11:30 UTC | May 13, 11:50 UTC | 20m |
| 2026-05-12 | FDB580 | CMB → DXB | May 12, 04:10 UTC | May 12, 05:05 UTC | 55m |
| 2026-05-10 | FDB1126 | TLV → DXB | May 10, 17:10 UTC | May 10, 18:25 UTC | 1h 15m |
| 2026-05-10 | FDB1126 | TLV → DXB | May 10, 15:09 UTC | May 10, 15:24 UTC | 15m |
| 2026-05-10 | FDB1125 | DXB → TLV | May 10, 12:30 UTC | May 10, 12:44 UTC | 15m |
| 2026-05-09 | FDB7UE | EVN → DXB | May 9, 08:45 UTC | May 9, 12:25 UTC | 3h 40m |
| 2026-05-09 | FDB59G | DXB → EVN | May 9, 06:00 UTC | May 9, 06:10 UTC | 10m |
| 2026-05-08 | FDB1082 | TLV → DXB | May 8, 14:45 UTC | May 8, 15:30 UTC | 45m |
| 2026-05-08 | FDB1082 | TLV → DXB | May 8, 12:49 UTC | May 8, 13:10 UTC | 20m |
| 2026-05-07 | FDB4CE | BEG → DXB | May 7, 21:50 UTC | May 8, 00:05 UTC | 2h 15m |
| 2026-05-07 | FDB14Q | DXB → BEG | May 7, 19:10 UTC | May 7, 20:25 UTC | 1h 15m |
| 2026-05-06 | FDB14Q | DXB → BEG | May 6, 22:55 UTC | May 7, 20:25 UTC | 21h 30m |
| 2026-05-05 | FDB7AF | DEL → DXB | May 5, 23:30 UTC | May 6, 00:05 UTC | 35m |
| 2026-05-05 | FDB441 | DXB → DEL | May 5, 18:55 UTC | May 5, 21:35 UTC | 2h 40m |
| 2026-05-05 | FDB620 | EBB → DXB | May 5, 13:10 UTC | May 5, 13:40 UTC | 30m |
| 2026-05-04 | FDB868 | DMM → DXB | May 4, 19:05 UTC | May 4, 20:25 UTC | 1h 20m |
| 2026-05-04 | FDB867 | DXB → DMM | May 4, 14:20 UTC | May 4, 15:10 UTC | 50m |
| 2026-05-03 | FDB2MF | IST → DXB | May 3, 19:05 UTC | May 3, 21:54 UTC | 2h 50m |
| 2026-05-03 | FDB4GP | DXB → IST | May 3, 10:15 UTC | May 3, 11:10 UTC | 55m |
| 2026-05-02 | FDB4TB | DXB → VKO | May 2, 14:05 UTC | May 2, 14:30 UTC | 25m |
| 2026-05-02 | FDB732 | ASB → DXB | May 2, 03:25 UTC | May 2, 03:55 UTC | 30m |
| 2026-05-01 | FDB731 | DXB → ASB | May 1, 17:55 UTC | May 1, 18:15 UTC | 20m |
| 2026-05-01 | FDB9DV | DXB → EBL | May 1, 07:30 UTC | May 1, 15:55 UTC | 8h 25m |
| 2026-04-30 | FDB176 | HBE → DXB | Apr 30, 21:15 UTC | May 1, 00:50 UTC | 3h 35m |
| 2026-04-30 | FDB175 | DXB → HBE | Apr 30, 15:10 UTC | Apr 30, 19:30 UTC | 4h 20m |
| 2026-04-30 | FDB932 | NUM → DXB | Apr 30, 04:25 UTC | Apr 30, 11:50 UTC | 7h 25m |
| 2026-04-29 | FDB3HP | BSR → DXB | Apr 29, 08:10 UTC | Apr 29, 16:30 UTC | 8h 21m |
| 2026-04-28 | FDB845 | DXB → RUH | Apr 28, 20:10 UTC | Apr 29, 01:25 UTC | 5h 15m |
| 2026-04-28 | FDB3DK | EBL → DXB | Apr 28, 07:00 UTC | Apr 28, 15:20 UTC | 8h 20m |
| 2026-04-26 | FDB2PM | DXB → BSR | Apr 26, 08:55 UTC | Apr 26, 17:00 UTC | 8h 5m |
| 2026-04-25 | FDB919 | DXB → JED | Apr 25, 22:05 UTC | Apr 26, 04:30 UTC | 6h 25m |
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-FMC page for operator, model, and routing details .