sensors Mode-S transponder
896606
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FKP · BOEING 737 MAX 8
- Hex
- 896606
- Octal
- 42263006
- Decimal
- 9,004,550
- Country
- AE
- Tail
- A6-FKP
- Type
- B38M
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 896606 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 |
|---|---|---|---|
| FDB3TH | Fly Dubai | 4 | 2026-05-07 |
| FDB3JE | Fly Dubai | 4 | 2026-05-27 |
| FDB175 | Fly Dubai | 4 | 2026-05-29 |
| FDB176 | Fly Dubai | 3 | 2026-05-22 |
| FDB920 | Fly Dubai | 2 | 2026-05-16 |
| FDB906 | Fly Dubai | 2 | 2026-04-20 |
| FDB905 | - | 2 | 2026-04-14 |
| FDB870 | Fly Dubai | 2 | 2026-05-19 |
| FDB5PG | Fly Dubai | 2 | 2026-05-26 |
| FDB5JA | Fly Dubai | 2 | 2026-04-30 |
| FDB579 | Fly Dubai | 2 | 2026-05-28 |
| FDB4JZ | Fly Dubai | 2 | 2026-04-24 |
| FDB446 | Fly Dubai | 2 | 2026-04-20 |
| FDB3YK | Fly Dubai | 2 | 2026-05-09 |
| FDB1KF | Fly Dubai | 2 | 2026-05-11 |
| FDB16T | Fly Dubai | 2 | 2026-04-27 |
| FDB9RQ | Fly Dubai | 1 | 2026-04-23 |
| FDB932 | Fly Dubai | 1 | 2026-05-02 |
| FDB914 | - | 1 | 2026-04-13 |
| FDB913 | Fly Dubai | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FDB822 | - | May 29, 21:15 UTC | May 30, 14:40 UTC | 17h 25m |
| 2026-05-29 | FDB175 | DXB → HBE | May 29, 04:20 UTC | May 29, 19:10 UTC | 14h 50m |
| 2026-05-28 | FDB579 | DXB → CMB | May 28, 13:00 UTC | May 29, 02:05 UTC | 13h 5m |
| 2026-05-28 | FDB579 | DXB → CMB | May 28, 06:45 UTC | May 29, 02:05 UTC | 19h 20m |
| 2026-05-27 | FDB5DN | ISU → DXB | May 27, 19:35 UTC | May 28, 13:45 UTC | 18h 10m |
| 2026-05-27 | FDB3JE | MRV → DXB | May 27, 17:40 UTC | May 28, 13:45 UTC | 20h 5m |
| 2026-05-27 | FDB3JE | MRV → DXB | May 27, 16:05 UTC | May 28, 13:45 UTC | 21h 40m |
| 2026-05-26 | FDB3JE | MRV → DXB | May 26, 18:30 UTC | May 27, 16:30 UTC | 22h 1m |
| 2026-05-26 | FDB5PG | DXB → MRV | May 26, 12:54 UTC | May 26, 18:45 UTC | 5h 50m |
| 2026-05-25 | FDB3JE | MRV → DXB | May 25, 02:00 UTC | May 25, 04:15 UTC | 2h 15m |
| 2026-05-23 | FDB5PG | DXB → MRV | May 23, 12:55 UTC | May 23, 20:45 UTC | 7h 50m |
| 2026-05-22 | FDB176 | HBE → DXB | May 22, 23:35 UTC | May 23, 20:45 UTC | 21h 10m |
| 2026-05-22 | FDB176 | HBE → DXB | May 22, 23:20 UTC | May 23, 20:45 UTC | 21h 25m |
| 2026-05-22 | FDB176 | HBE → DXB | May 22, 20:40 UTC | May 23, 12:55 UTC | 16h 14m |
| 2026-05-22 | FDB175 | DXB → HBE | May 22, 09:25 UTC | May 22, 19:15 UTC | 9h 50m |
| 2026-05-21 | FDB175 | DXB → HBE | May 21, 21:35 UTC | May 22, 19:15 UTC | 21h 40m |
| 2026-05-21 | FDB175 | DXB → HBE | May 21, 21:15 UTC | May 22, 19:15 UTC | 22h 0m |
| 2026-05-21 | FDB184 | HBE → DXB | May 21, 18:40 UTC | May 22, 16:30 UTC | 21h 50m |
| 2026-05-21 | FDB183 | DXB → HBE | May 21, 14:05 UTC | May 21, 17:10 UTC | 3h 5m |
| 2026-05-19 | FDB870 | DMM → DXB | May 19, 10:20 UTC | May 19, 11:10 UTC | 50m |
| 2026-05-16 | FDB920 | JED → DXB | May 16, 22:50 UTC | May 17, 03:45 UTC | 4h 55m |
| 2026-05-15 | FDB646 | ASM → DXB | May 15, 05:20 UTC | May 15, 22:05 UTC | 16h 44m |
| 2026-05-14 | FDB307 | DXB → KBL | May 14, 09:55 UTC | May 15, 05:25 UTC | 19h 30m |
| 2026-05-11 | FDB1KF | DXB → KHI | May 11, 03:45 UTC | May 11, 04:10 UTC | 25m |
| 2026-05-10 | FDB540 | KTM → DXB | May 10, 10:55 UTC | May 10, 13:25 UTC | 2h 30m |
| 2026-05-10 | FDB539 | DXB → KTM | May 10, 07:04 UTC | May 10, 08:35 UTC | 1h 30m |
| 2026-05-09 | FDB3YK | DXB → DOH | May 9, 12:55 UTC | May 9, 13:40 UTC | 45m |
| 2026-05-08 | FDB59J | BAH → DXB | May 8, 16:15 UTC | May 8, 17:05 UTC | 50m |
| 2026-05-08 | FDB5AY | DXB → BAH | May 8, 14:20 UTC | May 8, 14:40 UTC | 20m |
| 2026-05-07 | FDB3TH | DXB → BAH | May 7, 14:45 UTC | May 7, 15:05 UTC | 20m |
| 2026-05-05 | FDB7ZK | DOH → DXB | May 5, 17:00 UTC | May 5, 17:10 UTC | 10m |
| 2026-05-05 | FDB3YK | DXB → DOH | May 5, 13:35 UTC | May 5, 15:01 UTC | 1h 25m |
| 2026-05-05 | FDB920 | JED → DXB | May 5, 03:00 UTC | May 5, 03:30 UTC | 30m |
| 2026-05-04 | FDB870 | DMM → DXB | May 4, 10:10 UTC | May 4, 11:05 UTC | 55m |
| 2026-05-04 | FDB869 | DXB → DMM | May 4, 07:35 UTC | May 4, 08:30 UTC | 55m |
| 2026-05-02 | FDB932 | NUM → DXB | May 2, 20:15 UTC | May 3, 11:10 UTC | 14h 54m |
| 2026-05-02 | FDB43F | DXB → KHI | May 2, 15:40 UTC | May 2, 16:00 UTC | 20m |
| 2026-05-02 | FDB2GT | KHI → DXB | May 2, 08:10 UTC | May 2, 08:45 UTC | 35m |
| 2026-05-02 | FDB1KF | DXB → KHI | May 2, 03:35 UTC | May 2, 04:05 UTC | 30m |
| 2026-05-01 | FDB312 | KBL → DXB | May 1, 07:35 UTC | May 1, 07:55 UTC | 20m |
| 2026-05-01 | FDB311 | DXB → KBL | May 1, 00:40 UTC | May 1, 01:00 UTC | 20m |
| 2026-04-30 | FDB5JA | DXB → BEY | Apr 30, 07:15 UTC | Apr 30, 15:40 UTC | 8h 25m |
| 2026-04-29 | FDB5WB | BEY → DXB | Apr 29, 11:55 UTC | Apr 29, 15:05 UTC | 3h 10m |
| 2026-04-29 | FDB5JA | DXB → BEY | Apr 29, 06:49 UTC | Apr 29, 07:59 UTC | 1h 10m |
| 2026-04-28 | FDB3025 | - | Apr 28, 03:35 UTC | Apr 28, 19:35 UTC | 16h 0m |
| 2026-04-27 | FDB16T | BAH → DXB | Apr 27, 14:05 UTC | Apr 27, 15:00 UTC | 55m |
| 2026-04-27 | FDB3TH | DXB → BAH | Apr 27, 10:20 UTC | Apr 27, 11:15 UTC | 55m |
| 2026-04-26 | FDB864 | DMM → DXB | Apr 26, 13:30 UTC | Apr 26, 14:45 UTC | 1h 15m |
| 2026-04-26 | FDB863 | DXB → DMM | Apr 26, 08:55 UTC | Apr 26, 09:55 UTC | 1h 0m |
| 2026-04-25 | FDB16T | BAH → DXB | Apr 25, 14:45 UTC | Apr 25, 16:10 UTC | 1h 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-FKP page for operator, model, and routing details .