sensors Mode-S transponder
896688
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FPG · BOEING 737 MAX 8
- Hex
- 896688
- Octal
- 42263210
- Decimal
- 9,004,680
- Country
- AE
- Tail
- A6-FPG
- Type
- B38M
- Flights observed
- 74
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 896688 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 |
|---|---|---|---|
| FDB1736 | Fly Dubai | 8 | 2026-05-17 |
| FDB1735 | Fly Dubai | 8 | 2026-05-09 |
| FDB1690 | Fly Dubai | 6 | 2026-05-28 |
| FDB1941 | Fly Dubai | 5 | 2026-05-14 |
| FDB7UE | Fly Dubai | 4 | 2026-05-25 |
| FDB3DK | Fly Dubai | 4 | 2026-05-22 |
| FDB2RG | Fly Dubai | 4 | 2026-05-24 |
| FDB1942 | Fly Dubai | 4 | 2026-05-10 |
| FDB1689 | Fly Dubai | 4 | 2026-04-22 |
| FDB864 | Fly Dubai | 3 | 2026-05-10 |
| FDB863 | Fly Dubai | 3 | 2026-05-10 |
| FDB3PL | Fly Dubai | 3 | 2026-05-23 |
| FDB915 | Fly Dubai | 2 | 2026-04-25 |
| FDB59G | Fly Dubai | 2 | 2026-04-15 |
| FDB1114 | Fly Dubai | 2 | 2026-05-23 |
| FDB9CA | Fly Dubai | 1 | 2026-04-29 |
| FDB927 | - | 1 | 2026-04-19 |
| FDB746 | Fly Dubai | 1 | 2026-05-29 |
| FDB620 | Fly Dubai | 1 | 2026-04-22 |
| FDB619 | Fly Dubai | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB746 | TIA → DXB | May 29, 11:30 UTC | May 30, 02:45 UTC | 15h 15m |
| 2026-05-29 | FDB34Q | DXB → TIA | May 29, 05:00 UTC | May 29, 09:20 UTC | 4h 20m |
| 2026-05-28 | FDB1945 | DXB → TAS | May 28, 09:30 UTC | May 29, 05:05 UTC | 19h 35m |
| 2026-05-28 | FDB1690 | FRU → DXB | May 28, 01:30 UTC | May 28, 09:35 UTC | 8h 5m |
| 2026-05-27 | FDB1690 | FRU → DXB | May 27, 02:54 UTC | May 28, 01:35 UTC | 22h 40m |
| 2026-05-25 | FDB7UE | EVN → DXB | May 25, 14:45 UTC | May 25, 15:25 UTC | 40m |
| 2026-05-24 | FDB2RG | OTP → DXB | May 24, 16:05 UTC | May 25, 10:05 UTC | 18h 0m |
| 2026-05-24 | FDB2RG | OTP → DXB | May 24, 14:35 UTC | May 25, 10:05 UTC | 19h 30m |
| 2026-05-24 | FDB2RG | OTP → DXB | May 24, 12:15 UTC | May 25, 10:05 UTC | 21h 50m |
| 2026-05-23 | FDB3PL | DXB → OTP | May 23, 16:05 UTC | May 24, 10:50 UTC | 18h 45m |
| 2026-05-23 | FDB1114 | DAM → DXB | May 23, 14:20 UTC | May 24, 10:50 UTC | 20h 30m |
| 2026-05-23 | FDB1114 | DAM → DXB | May 23, 01:50 UTC | May 23, 16:30 UTC | 14h 40m |
| 2026-05-22 | FDB3DK | EBL → DXB | May 22, 14:20 UTC | May 23, 01:55 UTC | 11h 35m |
| 2026-05-22 | FDB3DK | EBL → DXB | May 22, 01:45 UTC | May 22, 15:05 UTC | 13h 20m |
| 2026-05-20 | FDB3DK | EBL → DXB | May 20, 14:35 UTC | May 21, 02:35 UTC | 12h 0m |
| 2026-05-19 | FDB3DK | EBL → DXB | May 19, 19:50 UTC | May 20, 15:15 UTC | 19h 26m |
| 2026-05-17 | FDB1690 | FRU → DXB | May 17, 19:45 UTC | May 18, 01:40 UTC | 5h 55m |
| 2026-05-17 | FDB1736 | ALA → DXB | May 17, 02:30 UTC | May 18, 01:40 UTC | 23h 10m |
| 2026-05-14 | FDB1941 | DXB → TAS | May 14, 20:10 UTC | May 15, 01:10 UTC | 5h 0m |
| 2026-05-10 | FDB1942 | TAS → DXB | May 10, 20:14 UTC | May 11, 01:30 UTC | 5h 15m |
| 2026-05-10 | FDB864 | DMM → DXB | May 10, 12:40 UTC | May 10, 13:40 UTC | 1h 0m |
| 2026-05-10 | FDB863 | DXB → DMM | May 10, 10:19 UTC | May 10, 10:30 UTC | 10m |
| 2026-05-09 | FDB1735 | DXB → ALA | May 9, 18:40 UTC | May 9, 18:55 UTC | 15m |
| 2026-05-06 | FDB1736 | ALA → DXB | May 6, 20:50 UTC | May 7, 02:25 UTC | 5h 35m |
| 2026-05-04 | FDB1735 | DXB → ALA | May 4, 19:10 UTC | May 4, 19:25 UTC | 15m |
| 2026-05-04 | FDB1736 | ALA → DXB | May 4, 04:55 UTC | May 4, 05:15 UTC | 20m |
| 2026-05-03 | FDB1735 | DXB → ALA | May 3, 18:34 UTC | May 3, 18:55 UTC | 20m |
| 2026-05-03 | FDB618 | JIB → DXB | May 3, 06:55 UTC | May 3, 14:55 UTC | 8h 0m |
| 2026-05-02 | FDB1941 | DXB → TAS | May 2, 18:05 UTC | May 3, 03:15 UTC | 9h 10m |
| 2026-05-02 | FDB1736 | ALA → DXB | May 2, 02:30 UTC | May 2, 05:00 UTC | 2h 30m |
| 2026-05-01 | FDB1735 | DXB → ALA | May 1, 18:30 UTC | May 1, 18:50 UTC | 20m |
| 2026-05-01 | FDB1942 | TAS → DXB | May 1, 01:05 UTC | May 1, 03:35 UTC | 2h 30m |
| 2026-04-30 | FDB1941 | DXB → TAS | Apr 30, 17:45 UTC | Apr 30, 18:05 UTC | 20m |
| 2026-04-29 | FDB5YA | VKO → DXB | Apr 29, 18:45 UTC | Apr 29, 21:05 UTC | 2h 20m |
| 2026-04-29 | FDB9CA | DXB → VKO | Apr 29, 05:15 UTC | Apr 29, 05:40 UTC | 25m |
| 2026-04-28 | FDB2RG | OTP → DXB | Apr 28, 12:15 UTC | Apr 28, 17:10 UTC | 4h 55m |
| 2026-04-28 | FDB3PL | DXB → OTP | Apr 28, 09:40 UTC | Apr 28, 10:10 UTC | 30m |
| 2026-04-28 | FDB3PL | DXB → OTP | Apr 28, 04:25 UTC | Apr 28, 05:35 UTC | 1h 10m |
| 2026-04-27 | FDB308 | KBL → DXB | Apr 27, 15:15 UTC | Apr 27, 15:40 UTC | 25m |
| 2026-04-27 | FDB307 | DXB → KBL | Apr 27, 07:55 UTC | Apr 27, 08:20 UTC | 25m |
| 2026-04-27 | FDB1942 | TAS → DXB | Apr 27, 03:10 UTC | Apr 27, 03:30 UTC | 20m |
| 2026-04-26 | FDB1941 | DXB → TAS | Apr 26, 17:45 UTC | Apr 26, 18:05 UTC | 20m |
| 2026-04-26 | FDB1736 | ALA → DXB | Apr 26, 04:20 UTC | Apr 26, 04:40 UTC | 20m |
| 2026-04-25 | FDB1735 | DXB → ALA | Apr 25, 18:25 UTC | Apr 25, 18:50 UTC | 25m |
| 2026-04-25 | FDB915 | DXB → EAM | Apr 25, 08:40 UTC | Apr 25, 14:30 UTC | 5h 50m |
| 2026-04-25 | FDB1942 | TAS → DXB | Apr 25, 03:00 UTC | Apr 25, 03:30 UTC | 30m |
| 2026-04-24 | FDB1941 | DXB → TAS | Apr 24, 17:45 UTC | Apr 24, 18:10 UTC | 25m |
| 2026-04-24 | FDB1736 | ALA → DXB | Apr 24, 04:40 UTC | Apr 24, 05:00 UTC | 20m |
| 2026-04-23 | FDB1735 | DXB → ALA | Apr 23, 18:20 UTC | Apr 23, 18:35 UTC | 15m |
| 2026-04-23 | FDB915 | DXB → EAM | Apr 23, 09:35 UTC | Apr 23, 15:40 UTC | 6h 5m |
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-FPG page for operator, model, and routing details .