sensors Mode-S transponder
8965C0
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPA · BOEING 737 MAX 8
- Hex
- 8965C0
- Octal
- 42262700
- Decimal
- 9,004,480
- Country
- AE
- Tail
- A6-FPA
- Type
- B38M
- Flights observed
- 100
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 8965C0 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 |
|---|---|---|---|
| FDB2MF | Fly Dubai | 4 | 2026-05-25 |
| FDB1114 | Fly Dubai | 4 | 2026-05-24 |
| FDB9CA | Fly Dubai | 3 | 2026-06-01 |
| FDB5WH | Fly Dubai | 3 | 2026-05-09 |
| FDB4GP | Fly Dubai | 3 | 2026-05-25 |
| FDB446 | Fly Dubai | 3 | 2026-05-16 |
| FDB1QV | Fly Dubai | 3 | 2026-05-08 |
| FDB1550 | Fly Dubai | 3 | 2026-05-12 |
| FDB1549 | Fly Dubai | 3 | 2026-05-12 |
| FDB1133 | Fly Dubai | 3 | 2026-04-30 |
| FDB989 | Fly Dubai | 2 | 2026-04-18 |
| FDB7UE | Fly Dubai | 2 | 2026-05-21 |
| FDB5WB | Fly Dubai | 2 | 2026-05-19 |
| FDB4TA | Fly Dubai | 2 | 2026-05-27 |
| FDB4CW | Fly Dubai | 2 | 2026-05-31 |
| FDB4CE | Fly Dubai | 2 | 2026-05-23 |
| FDB307 | Fly Dubai | 2 | 2026-04-24 |
| FDB2WK | Fly Dubai | 2 | 2026-05-09 |
| FDB1126 | Fly Dubai | 2 | 2026-04-29 |
| FDB1125 | Fly Dubai | 2 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FDB9CA | DXB → VKO | Jun 1, 18:10 UTC | Jun 2, 09:25 UTC | 15h 15m |
| 2026-06-01 | FDB9CA | DXB → VKO | Jun 1, 08:30 UTC | Jun 1, 18:15 UTC | 9h 45m |
| 2026-05-31 | FDB4CW | LJU → DXB | May 31, 14:05 UTC | Jun 1, 09:10 UTC | 19h 5m |
| 2026-05-31 | FDB4CW | LJU → DXB | May 31, 12:50 UTC | Jun 1, 09:10 UTC | 20h 20m |
| 2026-05-30 | FDB3NC | DXB → LJU | May 30, 04:30 UTC | May 30, 16:50 UTC | 12h 20m |
| 2026-05-30 | FDB2JQ | DXB → CCJ | May 30, 00:25 UTC | May 30, 00:45 UTC | 20m |
| 2026-05-27 | FDB4TA | ZAG → DXB | May 27, 12:55 UTC | May 28, 06:20 UTC | 17h 25m |
| 2026-05-26 | FDB7AF | DEL → DXB | May 26, 23:14 UTC | May 27, 06:15 UTC | 7h 0m |
| 2026-05-26 | FDB441 | DXB → DEL | May 26, 05:20 UTC | May 26, 21:34 UTC | 16h 15m |
| 2026-05-25 | FDB2MF | IST → DXB | May 25, 16:50 UTC | May 26, 05:40 UTC | 12h 49m |
| 2026-05-25 | FDB4GP | DXB → IST | May 25, 14:40 UTC | May 25, 14:50 UTC | 10m |
| 2026-05-25 | FDB5PS | TBS → DXB | May 25, 02:20 UTC | May 25, 06:05 UTC | 3h 45m |
| 2026-05-24 | FDB1114 | DAM → DXB | May 24, 15:30 UTC | May 24, 23:46 UTC | 8h 16m |
| 2026-05-24 | FDB1114 | DAM → DXB | May 24, 02:30 UTC | May 24, 23:46 UTC | 21h 16m |
| 2026-05-24 | FDB1114 | DAM → DXB | May 24, 00:05 UTC | May 24, 23:46 UTC | 23h 41m |
| 2026-05-23 | FDB4CE | BEG → DXB | May 23, 22:05 UTC | May 24, 16:15 UTC | 18h 10m |
| 2026-05-23 | FDB4CE | BEG → DXB | May 23, 21:55 UTC | May 24, 16:15 UTC | 18h 20m |
| 2026-05-23 | FDB5GE | OTP → DXB | May 23, 06:40 UTC | May 23, 20:05 UTC | 13h 25m |
| 2026-05-23 | FDB1NU | DXB → OTP | May 23, 03:10 UTC | May 23, 05:00 UTC | 1h 50m |
| 2026-05-21 | FDB7UE | EVN → DXB | May 21, 08:50 UTC | May 22, 02:45 UTC | 17h 55m |
| 2026-05-19 | FDB5WB | BEY → DXB | May 19, 14:25 UTC | May 19, 15:10 UTC | 45m |
| 2026-05-18 | FDB846 | RUH → DXB | May 18, 08:20 UTC | May 19, 00:45 UTC | 16h 24m |
| 2026-05-17 | FDB4TA | ZAG → DXB | May 17, 13:05 UTC | May 17, 17:45 UTC | 4h 40m |
| 2026-05-17 | FDB4MA | DXB → ZAG | May 17, 10:00 UTC | May 17, 11:40 UTC | 1h 40m |
| 2026-05-16 | FDB446 | BOM → DXB | May 16, 00:20 UTC | May 16, 01:10 UTC | 50m |
| 2026-05-15 | FDB5WB | BEY → DXB | May 15, 12:20 UTC | May 15, 22:25 UTC | 10h 4m |
| 2026-05-14 | FDB2MY | AMD → DXB | May 14, 23:10 UTC | May 15, 00:05 UTC | 55m |
| 2026-05-14 | FDB2FL | DXB → BGW | May 14, 05:35 UTC | May 14, 21:20 UTC | 15h 45m |
| 2026-05-12 | FDB454 | COK → DXB | May 12, 21:55 UTC | May 12, 22:20 UTC | 25m |
| 2026-05-12 | FDB1550 | TLV → DXB | May 12, 08:05 UTC | May 12, 20:15 UTC | 12h 10m |
| 2026-05-12 | FDB1549 | DXB → TLV | May 12, 05:10 UTC | May 12, 05:45 UTC | 35m |
| 2026-05-10 | FDB3PR | SOF → DXB | May 10, 12:40 UTC | May 10, 16:55 UTC | 4h 15m |
| 2026-05-09 | FDB5WH | DXB → SOF | May 9, 16:05 UTC | May 10, 11:00 UTC | 18h 55m |
| 2026-05-09 | FDB5WH | DXB → SOF | May 9, 15:35 UTC | May 10, 11:00 UTC | 19h 25m |
| 2026-05-09 | FDB5WH | DXB → SOF | May 9, 12:40 UTC | May 10, 11:00 UTC | 22h 20m |
| 2026-05-09 | FDB2WK | DXB → TBS | May 9, 07:15 UTC | May 9, 10:35 UTC | 3h 20m |
| 2026-05-08 | FDB1QV | EVN → DXB | May 8, 14:15 UTC | May 9, 10:35 UTC | 20h 20m |
| 2026-05-08 | FDB1QV | EVN → DXB | May 8, 12:49 UTC | May 9, 10:35 UTC | 21h 45m |
| 2026-05-08 | FDB1QV | EVN → DXB | May 8, 11:25 UTC | May 9, 07:25 UTC | 20h 0m |
| 2026-05-06 | FDB1114 | DAM → DXB | May 6, 14:15 UTC | May 6, 16:25 UTC | 2h 10m |
| 2026-05-05 | FDB1687 | ZNZ → DAR | May 5, 07:50 UTC | May 6, 00:01 UTC | 16h 10m |
| 2026-05-04 | FDB830 | JED → DXB | May 4, 21:10 UTC | May 4, 21:20 UTC | 10m |
| 2026-05-04 | FDB829 | DXB → JED | May 4, 10:45 UTC | May 4, 20:15 UTC | 9h 31m |
| 2026-05-03 | FDB71T | TBS → DXB | May 3, 12:50 UTC | May 3, 17:10 UTC | 4h 20m |
| 2026-05-03 | FDB2WK | DXB → TBS | May 3, 07:00 UTC | May 3, 10:50 UTC | 3h 50m |
| 2026-05-03 | FDB446 | BOM → DXB | May 3, 02:25 UTC | May 3, 02:55 UTC | 30m |
| 2026-05-03 | FDB446 | BOM → DXB | May 3, 00:20 UTC | May 3, 00:35 UTC | 15m |
| 2026-05-02 | FDB445 | DXB → BOM | May 2, 21:55 UTC | May 2, 22:55 UTC | 1h 0m |
| 2026-05-02 | FDB1BH | TBS → DXB | May 2, 08:40 UTC | May 2, 12:40 UTC | 4h 0m |
| 2026-05-02 | FDB4XN | DXB → TBS | May 2, 02:35 UTC | May 2, 07:00 UTC | 4h 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-FPA page for operator, model, and routing details .