sensors Mode-S transponder
896516
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FNC · BOEING 737 MAX 9
- Hex
- 896516
- Octal
- 42262426
- Decimal
- 9,004,310
- Country
- AE
- Tail
- A6-FNC
- Type
- B39M
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 47m ago
Last known position
Country allocation
The ICAO 24-bit address 896516 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 |
|---|---|---|---|
| FDB856 | Fly Dubai | 11 | 2026-05-28 |
| FDB846 | Fly Dubai | 8 | 2026-05-09 |
| FDB1550 | Fly Dubai | 6 | 2026-05-29 |
| FDB842 | Fly Dubai | 5 | 2026-05-19 |
| FDB2FL | Fly Dubai | 5 | 2026-05-01 |
| FDB1126 | Fly Dubai | 5 | 2026-05-26 |
| FDB869 | Fly Dubai | 4 | 2026-04-27 |
| FDB841 | Fly Dubai | 4 | 2026-04-29 |
| FDB1815 | Fly Dubai | 4 | 2026-05-27 |
| FDB870 | Fly Dubai | 3 | 2026-04-27 |
| FDB868 | Fly Dubai | 3 | 2026-05-25 |
| FDB855 | Fly Dubai | 3 | 2026-04-30 |
| FDB847 | Fly Dubai | 3 | 2026-05-17 |
| FDB845 | Fly Dubai | 3 | 2026-05-09 |
| FDB1735 | Fly Dubai | 3 | 2026-04-27 |
| FDB1549 | Fly Dubai | 3 | 2026-05-07 |
| FDB1212 | Fly Dubai | 3 | 2026-05-20 |
| FDB1125 | Fly Dubai | 3 | 2026-05-26 |
| FDB848 | Fly Dubai | 2 | 2026-04-15 |
| FDB7RC | Fly Dubai | 2 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB1406 | BUD → DXB | May 29, 21:05 UTC | May 30, 19:30 UTC | 22h 25m |
| 2026-05-29 | FDB1405 | DXB → BUD | May 29, 14:15 UTC | May 29, 19:15 UTC | 5h 0m |
| 2026-05-29 | FDB1550 | TLV → DXB | May 29, 08:25 UTC | May 29, 08:45 UTC | 20m |
| 2026-05-28 | FDB856 | RUH → DXB | May 28, 18:45 UTC | May 29, 06:45 UTC | 12h 0m |
| 2026-05-28 | FDB1550 | TLV → DXB | May 28, 10:05 UTC | May 29, 06:45 UTC | 20h 40m |
| 2026-05-28 | FDB1550 | TLV → DXB | May 28, 08:15 UTC | May 28, 08:35 UTC | 20m |
| 2026-05-27 | FDB1815 | JMK → JTR | May 27, 14:40 UTC | May 28, 06:40 UTC | 16h 0m |
| 2026-05-27 | FDB1815 | JMK → JTR | May 27, 12:25 UTC | May 27, 12:40 UTC | 15m |
| 2026-05-26 | FDB1126 | TLV → DXB | May 26, 17:15 UTC | May 26, 17:55 UTC | 40m |
| 2026-05-26 | FDB1126 | TLV → DXB | May 26, 15:20 UTC | May 26, 15:45 UTC | 25m |
| 2026-05-26 | FDB1125 | DXB → TLV | May 26, 12:45 UTC | May 26, 13:15 UTC | 30m |
| 2026-05-25 | FDB868 | DMM → DXB | May 25, 16:50 UTC | May 25, 17:40 UTC | 50m |
| 2026-05-24 | FDB1815 | JMK → JTR | May 24, 14:50 UTC | May 25, 08:05 UTC | 17h 15m |
| 2026-05-24 | FDB1815 | JMK → JTR | May 24, 12:50 UTC | May 24, 13:05 UTC | 15m |
| 2026-05-23 | FDB7RC | DXB → JMK | May 23, 17:35 UTC | May 24, 11:35 UTC | 18h 0m |
| 2026-05-23 | FDB7RC | DXB → JMK | May 23, 17:00 UTC | May 24, 11:35 UTC | 18h 35m |
| 2026-05-23 | FDB1126 | TLV → DXB | May 23, 15:10 UTC | May 23, 15:35 UTC | 25m |
| 2026-05-23 | FDB1125 | DXB → TLV | May 23, 13:00 UTC | May 23, 13:20 UTC | 20m |
| 2026-05-23 | FDB884 | DMM → DXB | May 23, 05:55 UTC | May 23, 06:55 UTC | 1h 0m |
| 2026-05-22 | FDB856 | RUH → DXB | May 22, 18:40 UTC | May 22, 19:15 UTC | 35m |
| 2026-05-21 | FDB856 | RUH → DXB | May 21, 19:00 UTC | May 21, 19:25 UTC | 25m |
| 2026-05-20 | FDB856 | RUH → DXB | May 20, 20:50 UTC | May 21, 19:25 UTC | 22h 35m |
| 2026-05-20 | FDB1212 | TLV → DXB | May 20, 14:05 UTC | May 20, 21:10 UTC | 7h 5m |
| 2026-05-20 | FDB1212 | TLV → DXB | May 20, 12:25 UTC | May 20, 12:40 UTC | 15m |
| 2026-05-19 | FDB842 | RUH → DXB | May 19, 11:50 UTC | May 19, 12:15 UTC | 25m |
| 2026-05-18 | FDB842 | RUH → DXB | May 18, 15:45 UTC | May 19, 12:15 UTC | 20h 29m |
| 2026-05-18 | FDB842 | RUH → DXB | May 18, 08:05 UTC | May 18, 15:55 UTC | 7h 50m |
| 2026-05-17 | FDB847 | DXB → RUH | May 17, 04:30 UTC | May 17, 04:40 UTC | 10m |
| 2026-05-14 | FDB856 | RUH → DXB | May 14, 19:25 UTC | May 15, 08:00 UTC | 12h 35m |
| 2026-05-14 | FDB856 | RUH → DXB | May 14, 12:50 UTC | May 15, 08:00 UTC | 19h 10m |
| 2026-05-14 | FDB1212 | TLV → DXB | May 14, 10:50 UTC | May 14, 11:10 UTC | 20m |
| 2026-05-14 | FDB1211 | DXB → TLV | May 14, 08:55 UTC | May 14, 09:10 UTC | 15m |
| 2026-05-14 | FDB1211 | DXB → TLV | May 14, 06:10 UTC | May 14, 07:05 UTC | 55m |
| 2026-05-13 | FDB7ZK | DOH → DXB | May 13, 15:45 UTC | May 13, 16:30 UTC | 45m |
| 2026-05-12 | FDB856 | RUH → DXB | May 12, 18:45 UTC | May 13, 08:25 UTC | 13h 40m |
| 2026-05-11 | FDB1126 | TLV → DXB | May 11, 17:15 UTC | May 11, 17:50 UTC | 35m |
| 2026-05-11 | FDB1126 | TLV → DXB | May 11, 15:15 UTC | May 11, 15:30 UTC | 15m |
| 2026-05-11 | FDB1125 | DXB → TLV | May 11, 12:45 UTC | May 11, 13:10 UTC | 25m |
| 2026-05-10 | FDB1114 | DAM → DXB | May 10, 15:35 UTC | May 11, 10:50 UTC | 19h 15m |
| 2026-05-09 | FDB846 | RUH → DXB | May 9, 23:55 UTC | May 10, 16:04 UTC | 16h 10m |
| 2026-05-09 | FDB845 | DXB → RUH | May 9, 20:15 UTC | May 10, 16:04 UTC | 19h 50m |
| 2026-05-09 | FDB1082 | TLV → DXB | May 9, 12:55 UTC | May 9, 15:30 UTC | 2h 35m |
| 2026-05-09 | FDB1081 | DXB → TLV | May 9, 10:30 UTC | May 9, 10:45 UTC | 15m |
| 2026-05-08 | FDB846 | RUH → DXB | May 8, 15:40 UTC | May 9, 08:35 UTC | 16h 55m |
| 2026-05-08 | FDB71T | TBS → DXB | May 8, 12:49 UTC | May 9, 08:35 UTC | 19h 45m |
| 2026-05-07 | FDB2WK | DXB → TBS | May 7, 19:05 UTC | May 8, 10:54 UTC | 15h 50m |
| 2026-05-07 | FDB1550 | TLV → DXB | May 7, 08:05 UTC | May 7, 19:30 UTC | 11h 25m |
| 2026-05-07 | FDB1549 | DXB → TLV | May 7, 06:05 UTC | May 7, 06:25 UTC | 20m |
| 2026-05-06 | FDB856 | RUH → DXB | May 6, 11:25 UTC | May 6, 19:30 UTC | 8h 4m |
| 2026-05-05 | FDB846 | RUH → DXB | May 5, 23:50 UTC | May 6, 01:10 UTC | 1h 20m |
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-FNC page for operator, model, and routing details .