sensors Mode-S transponder
8965C3
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPD · BOEING 737 MAX 8
- Hex
- 8965C3
- Octal
- 42262703
- Decimal
- 9,004,483
- Country
- AE
- Tail
- A6-FPD
- Type
- B38M
- Flights observed
- 97
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8965C3 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 |
|---|---|---|---|
| FDB1133 | Fly Dubai | 4 | 2026-05-03 |
| FDB1114 | Fly Dubai | 4 | 2026-05-18 |
| FDB5WH | Fly Dubai | 3 | 2026-04-19 |
| FDB579 | Fly Dubai | 3 | 2026-05-21 |
| FDB3PR | Fly Dubai | 3 | 2026-04-19 |
| FDB1QV | Fly Dubai | 3 | 2026-05-06 |
| FDB1134 | Fly Dubai | 3 | 2026-05-04 |
| FDB1026 | Fly Dubai | 3 | 2026-05-25 |
| FDB1025 | Fly Dubai | 3 | 2026-05-26 |
| FDB9UR | Fly Dubai | 2 | 2026-05-02 |
| FDB732 | Fly Dubai | 2 | 2026-05-03 |
| FDB65E | Fly Dubai | 2 | 2026-04-26 |
| FDB5YA | Fly Dubai | 2 | 2026-04-23 |
| FDB580 | Fly Dubai | 2 | 2026-05-21 |
| FDB573 | Fly Dubai | 2 | 2026-05-04 |
| FDB461 | Fly Dubai | 2 | 2026-05-01 |
| FDB3CK | Fly Dubai | 2 | 2026-04-15 |
| FDB34Q | Fly Dubai | 2 | 2026-05-15 |
| FDB1KF | Fly Dubai | 2 | 2026-04-29 |
| FDB1BM | - | 2 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FDB928 | - | May 28, 07:25 UTC | May 28, 13:20 UTC | 5h 55m |
| 2026-05-27 | FDB1502 | CTA → DXB | May 27, 10:45 UTC | May 27, 21:35 UTC | 10h 50m |
| 2026-05-26 | FDB7KL | AMM → DXB | May 26, 21:25 UTC | May 27, 07:50 UTC | 10h 26m |
| 2026-05-26 | FDB1025 | DXB → MLE | May 26, 04:10 UTC | May 26, 18:24 UTC | 14h 15m |
| 2026-05-25 | FDB1026 | MLE → DXB | May 25, 06:35 UTC | May 26, 04:20 UTC | 21h 44m |
| 2026-05-24 | FDB3XU | KRK → DXB | May 24, 10:55 UTC | May 25, 06:45 UTC | 19h 50m |
| 2026-05-24 | FDB4GA | DXB → KRK | May 24, 07:30 UTC | May 24, 09:10 UTC | 1h 40m |
| 2026-05-22 | FDB1KS | BEG → DXB | May 22, 12:20 UTC | May 22, 15:05 UTC | 2h 45m |
| 2026-05-22 | FDB9YD | DXB → BEG | May 22, 10:15 UTC | May 22, 10:25 UTC | 10m |
| 2026-05-21 | FDB580 | CMB → DXB | May 21, 04:20 UTC | May 21, 05:00 UTC | 40m |
| 2026-05-21 | FDB579 | DXB → CMB | May 21, 01:30 UTC | May 21, 02:05 UTC | 35m |
| 2026-05-18 | FDB1114 | DAM → DXB | May 18, 16:35 UTC | May 18, 16:45 UTC | 10m |
| 2026-05-16 | FDB1114 | DAM → DXB | May 16, 22:55 UTC | May 17, 16:01 UTC | 17h 5m |
| 2026-05-16 | FDB1114 | DAM → DXB | May 16, 16:50 UTC | May 17, 16:01 UTC | 23h 10m |
| 2026-05-16 | FDB444 | LKO → DXB | May 16, 03:25 UTC | May 17, 02:35 UTC | 23h 10m |
| 2026-05-15 | FDB746 | TIA → DXB | May 15, 11:50 UTC | May 16, 00:55 UTC | 13h 4m |
| 2026-05-15 | FDB34Q | DXB → TIA | May 15, 05:10 UTC | May 15, 09:45 UTC | 4h 35m |
| 2026-05-14 | FDB34Q | DXB → TIA | May 14, 11:25 UTC | May 15, 09:45 UTC | 22h 20m |
| 2026-05-14 | FDB7UE | EVN → DXB | May 14, 08:50 UTC | May 15, 05:15 UTC | 20h 25m |
| 2026-05-12 | FDB3DK | EBL → DXB | May 12, 21:25 UTC | May 13, 14:30 UTC | 17h 5m |
| 2026-05-12 | FDB822 | - | May 12, 14:05 UTC | May 13, 01:10 UTC | 11h 5m |
| 2026-05-11 | FDB5GE | OTP → DXB | May 11, 06:50 UTC | May 11, 11:10 UTC | 4h 20m |
| 2026-05-11 | FDB1NU | DXB → OTP | May 11, 00:10 UTC | May 11, 04:55 UTC | 4h 45m |
| 2026-05-10 | FDB3KJ | MBA → DXB | May 10, 16:04 UTC | May 10, 16:25 UTC | 20m |
| 2026-05-09 | FDB1BM | - | May 9, 16:50 UTC | May 10, 16:25 UTC | 23h 35m |
| 2026-05-09 | FDB1BM | - | May 9, 12:20 UTC | May 9, 17:15 UTC | 4h 55m |
| 2026-05-08 | FDB52X | DXB → SJJ | May 8, 21:15 UTC | May 9, 10:40 UTC | 13h 25m |
| 2026-05-07 | FDB454 | COK → DXB | May 7, 21:05 UTC | May 7, 21:30 UTC | 25m |
| 2026-05-07 | FDB848 | RUH → DXB | May 7, 08:10 UTC | May 7, 19:10 UTC | 11h 0m |
| 2026-05-06 | FDB1QV | EVN → DXB | May 6, 14:05 UTC | May 7, 08:45 UTC | 18h 40m |
| 2026-05-06 | FDB1QV | EVN → DXB | May 6, 12:40 UTC | May 7, 08:45 UTC | 20h 5m |
| 2026-05-06 | FDB1QV | EVN → DXB | May 6, 07:20 UTC | May 6, 16:20 UTC | 9h 0m |
| 2026-05-05 | FDB1550 | TLV → DXB | May 5, 10:05 UTC | May 5, 22:30 UTC | 12h 25m |
| 2026-05-05 | FDB1550 | TLV → DXB | May 5, 08:05 UTC | May 5, 08:20 UTC | 15m |
| 2026-05-05 | FDB1549 | DXB → TLV | May 5, 06:10 UTC | May 5, 06:35 UTC | 25m |
| 2026-05-04 | FDB574 | KTM → DXB | May 4, 17:40 UTC | May 4, 19:30 UTC | 1h 51m |
| 2026-05-04 | FDB573 | DXB → KTM | May 4, 15:05 UTC | May 4, 15:50 UTC | 45m |
| 2026-05-04 | FDB573 | DXB → KTM | May 4, 12:05 UTC | May 4, 12:20 UTC | 15m |
| 2026-05-04 | FDB1134 | KTM → DXB | May 4, 04:24 UTC | May 4, 08:45 UTC | 4h 20m |
| 2026-05-03 | FDB1133 | DXB → KTM | May 3, 22:25 UTC | May 4, 02:00 UTC | 3h 35m |
| 2026-05-03 | FDB1114 | DAM → DXB | May 3, 09:15 UTC | May 3, 17:45 UTC | 8h 30m |
| 2026-05-03 | FDB732 | ASB → DXB | May 3, 03:40 UTC | May 3, 04:20 UTC | 40m |
| 2026-05-02 | FDB9UR | CCU → DXB | May 2, 00:15 UTC | May 2, 00:45 UTC | 30m |
| 2026-05-01 | FDB9UR | CCU → DXB | May 1, 20:10 UTC | May 1, 20:55 UTC | 45m |
| 2026-05-01 | FDB461 | DXB → CCU | May 1, 17:50 UTC | May 1, 18:35 UTC | 45m |
| 2026-05-01 | FDB461 | DXB → CCU | May 1, 14:45 UTC | May 1, 15:05 UTC | 20m |
| 2026-05-01 | FDB354 | ISB → DXB | May 1, 03:45 UTC | May 1, 04:05 UTC | 20m |
| 2026-04-30 | FDB353 | DXB → ISB | Apr 30, 20:25 UTC | Apr 30, 20:50 UTC | 25m |
| 2026-04-30 | FDB868 | DMM → DXB | Apr 30, 17:05 UTC | Apr 30, 18:00 UTC | 55m |
| 2026-04-30 | FDB867 | DXB → DMM | Apr 30, 14:25 UTC | Apr 30, 15:25 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-FPD page for operator, model, and routing details .