sensors Mode-S transponder
8965C2
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPC · BOEING 737 MAX 8
- Hex
- 8965C2
- Octal
- 42262702
- Decimal
- 9,004,482
- Country
- AE
- Tail
- A6-FPC
- Type
- B38M
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8965C2 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 |
|---|---|---|---|
| FDB441 | Fly Dubai | 7 | 2026-05-17 |
| FDB7AF | Fly Dubai | 5 | 2026-04-29 |
| FDB7XZ | Fly Dubai | 4 | 2026-05-18 |
| FDB573 | Fly Dubai | 4 | 2026-05-20 |
| FDB312 | Fly Dubai | 3 | 2026-04-27 |
| FDB14Q | Fly Dubai | 3 | 2026-05-15 |
| FDB884 | Fly Dubai | 2 | 2026-04-18 |
| FDB868 | Fly Dubai | 2 | 2026-04-27 |
| FDB867 | Fly Dubai | 2 | 2026-04-27 |
| FDB822 | - | 2 | 2026-04-16 |
| FDB62H | Fly Dubai | 2 | 2026-04-17 |
| FDB59K | - | 2 | 2026-04-14 |
| FDB59G | Fly Dubai | 2 | 2026-04-24 |
| FDB574 | Fly Dubai | 2 | 2026-05-20 |
| FDB540 | Fly Dubai | 2 | 2026-05-09 |
| FDB539 | Fly Dubai | 2 | 2026-05-09 |
| FDB446 | Fly Dubai | 2 | 2026-05-10 |
| FDB435 | Fly Dubai | 2 | 2026-05-16 |
| FDB3YX | - | 2 | 2026-04-14 |
| FDB311 | Fly Dubai | 2 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB818 | - | May 28, 14:55 UTC | May 28, 15:35 UTC | 40m |
| 2026-05-26 | FDB34Q | DXB → TIA | May 26, 21:44 UTC | May 27, 09:05 UTC | 11h 21m |
| 2026-05-24 | FDB3PR | SOF → DXB | May 24, 13:40 UTC | May 25, 03:25 UTC | 13h 45m |
| 2026-05-23 | FDB1406 | BUD → DXB | May 23, 21:30 UTC | May 24, 12:10 UTC | 14h 40m |
| 2026-05-22 | FDB1405 | DXB → BUD | May 22, 17:40 UTC | May 22, 18:50 UTC | 1h 10m |
| 2026-05-20 | FDB574 | KTM → DXB | May 20, 18:35 UTC | May 20, 21:20 UTC | 2h 45m |
| 2026-05-20 | FDB573 | DXB → KTM | May 20, 09:30 UTC | May 20, 16:40 UTC | 7h 10m |
| 2026-05-19 | FDB573 | DXB → KTM | May 19, 16:35 UTC | May 20, 16:30 UTC | 23h 56m |
| 2026-05-19 | FDB1636 | TLV → DXB | May 19, 15:50 UTC | May 20, 10:10 UTC | 18h 21m |
| 2026-05-19 | FDB1636 | TLV → DXB | May 19, 14:15 UTC | May 19, 14:30 UTC | 15m |
| 2026-05-19 | FDB1635 | DXB → TLV | May 19, 12:50 UTC | May 19, 13:05 UTC | 15m |
| 2026-05-18 | FDB1ZA | SPX → DXB | May 18, 23:20 UTC | May 18, 23:30 UTC | 10m |
| 2026-05-18 | FDB7XZ | BGW → DXB | May 18, 11:55 UTC | May 18, 21:40 UTC | 9h 44m |
| 2026-05-17 | FDB7XZ | BGW → DXB | May 17, 22:50 UTC | May 18, 21:40 UTC | 22h 49m |
| 2026-05-17 | FDB441 | DXB → DEL | May 17, 20:35 UTC | May 17, 21:15 UTC | 40m |
| 2026-05-16 | FDB436 | HYD → DXB | May 16, 22:35 UTC | May 17, 21:15 UTC | 22h 40m |
| 2026-05-16 | FDB435 | DXB → HYD | May 16, 18:35 UTC | May 16, 23:20 UTC | 4h 45m |
| 2026-05-15 | FDB4CE | BEG → DXB | May 15, 22:10 UTC | May 16, 02:25 UTC | 4h 15m |
| 2026-05-15 | FDB14Q | DXB → BEG | May 15, 15:40 UTC | May 15, 20:40 UTC | 5h 0m |
| 2026-05-15 | FDB14Q | DXB → BEG | May 15, 00:50 UTC | May 15, 20:40 UTC | 19h 49m |
| 2026-05-14 | FDB14Q | DXB → BEG | May 14, 21:30 UTC | May 15, 20:30 UTC | 22h 59m |
| 2026-05-13 | FDB1114 | DAM → DXB | May 13, 09:50 UTC | May 13, 16:20 UTC | 6h 30m |
| 2026-05-12 | FDB1942 | TAS → DXB | May 12, 20:10 UTC | May 13, 01:05 UTC | 4h 55m |
| 2026-05-10 | FDB446 | BOM → DXB | May 10, 21:40 UTC | May 11, 01:05 UTC | 3h 25m |
| 2026-05-09 | FDB540 | KTM → DXB | May 9, 10:10 UTC | May 9, 12:40 UTC | 2h 30m |
| 2026-05-09 | FDB539 | DXB → KTM | May 9, 07:10 UTC | May 9, 08:05 UTC | 55m |
| 2026-05-08 | FDB540 | KTM → DXB | May 8, 10:44 UTC | May 9, 08:05 UTC | 21h 20m |
| 2026-05-08 | FDB539 | DXB → KTM | May 8, 08:14 UTC | May 8, 09:09 UTC | 55m |
| 2026-05-07 | FDB842 | RUH → DXB | May 7, 12:35 UTC | May 8, 09:09 UTC | 20h 35m |
| 2026-05-04 | FDB1QV | EVN → DXB | May 4, 20:40 UTC | May 4, 21:20 UTC | 40m |
| 2026-05-04 | FDB1QV | EVN → DXB | May 4, 05:25 UTC | May 4, 15:35 UTC | 10h 10m |
| 2026-05-02 | FDB7XZ | BGW → DXB | May 2, 19:40 UTC | May 3, 13:10 UTC | 17h 29m |
| 2026-05-02 | FDB7XZ | BGW → DXB | May 2, 17:35 UTC | May 3, 13:10 UTC | 19h 34m |
| 2026-05-02 | FDB446 | BOM → DXB | May 2, 00:10 UTC | May 2, 02:45 UTC | 2h 35m |
| 2026-05-01 | FDB445 | DXB → BOM | May 1, 19:45 UTC | May 1, 22:15 UTC | 2h 30m |
| 2026-05-01 | FDB5WB | BEY → DXB | May 1, 12:10 UTC | May 1, 15:30 UTC | 3h 20m |
| 2026-05-01 | FDB5JA | DXB → BEY | May 1, 06:45 UTC | May 1, 09:55 UTC | 3h 10m |
| 2026-05-01 | FDB2MY | AMD → DXB | May 1, 00:55 UTC | May 1, 01:20 UTC | 25m |
| 2026-04-30 | FDB437 | DXB → AMD | Apr 30, 19:00 UTC | Apr 30, 19:20 UTC | 20m |
| 2026-04-30 | FDB9DV | DXB → EBL | Apr 30, 07:20 UTC | Apr 30, 15:30 UTC | 8h 10m |
| 2026-04-29 | FDB7AF | DEL → DXB | Apr 29, 22:50 UTC | Apr 30, 02:05 UTC | 3h 14m |
| 2026-04-29 | FDB441 | DXB → DEL | Apr 29, 20:25 UTC | Apr 29, 21:05 UTC | 40m |
| 2026-04-29 | FDB441 | DXB → DEL | Apr 29, 18:20 UTC | Apr 29, 18:40 UTC | 20m |
| 2026-04-29 | FDB620 | EBB → DXB | Apr 29, 01:20 UTC | Apr 29, 13:20 UTC | 12h 1m |
| 2026-04-28 | FDB829 | DXB → JED | Apr 28, 11:30 UTC | Apr 28, 18:05 UTC | 6h 35m |
| 2026-04-27 | FDB868 | DMM → DXB | Apr 27, 16:55 UTC | Apr 27, 17:55 UTC | 1h 0m |
| 2026-04-27 | FDB867 | DXB → DMM | Apr 27, 13:05 UTC | Apr 27, 13:50 UTC | 45m |
| 2026-04-27 | FDB312 | KBL → DXB | Apr 27, 07:05 UTC | Apr 27, 07:25 UTC | 20m |
| 2026-04-27 | FDB311 | DXB → KBL | Apr 27, 00:20 UTC | Apr 27, 00:40 UTC | 20m |
| 2026-04-26 | FDB868 | DMM → DXB | Apr 26, 16:55 UTC | Apr 26, 17:55 UTC | 1h 0m |
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-FPC page for operator, model, and routing details .