sensors Mode-S transponder
896517
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FMH · BOEING 737 MAX 8
- Hex
- 896517
- Octal
- 42262427
- Decimal
- 9,004,311
- Country
- AE
- Tail
- A6-FMH
- Type
- B38M
- Flights observed
- 84
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 896517 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 |
|---|---|---|---|
| FDB3PL | Fly Dubai | 5 | 2026-05-31 |
| FDB2RG | Fly Dubai | 5 | 2026-05-29 |
| FDB7MN | Fly Dubai | 3 | 2026-05-03 |
| FDB7KL | Fly Dubai | 3 | 2026-05-12 |
| FDB4GP | Fly Dubai | 3 | 2026-05-22 |
| FDB435 | Fly Dubai | 3 | 2026-04-29 |
| FDB882 | Fly Dubai | 2 | 2026-05-19 |
| FDB848 | Fly Dubai | 2 | 2026-05-28 |
| FDB732 | Fly Dubai | 2 | 2026-04-27 |
| FDB731 | Fly Dubai | 2 | 2026-04-26 |
| FDB71T | Fly Dubai | 2 | 2026-05-10 |
| FDB64C | Fly Dubai | 2 | 2026-06-01 |
| FDB580 | Fly Dubai | 2 | 2026-05-02 |
| FDB436 | Fly Dubai | 2 | 2026-04-29 |
| FDB34Q | Fly Dubai | 2 | 2026-06-05 |
| FDB2MF | Fly Dubai | 2 | 2026-05-22 |
| FDB1134 | Fly Dubai | 2 | 2026-06-03 |
| FDB9DV | Fly Dubai | 1 | 2026-04-22 |
| FDB870 | Fly Dubai | 1 | 2026-04-29 |
| FDB869 | Fly Dubai | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-05 | FDB34Q | DXB → TIA | Jun 5, 11:35 UTC | Jun 6, 08:30 UTC | 20h 55m |
| 2026-06-05 | FDB3UM | DXB → NAP | Jun 5, 04:30 UTC | Jun 5, 09:15 UTC | 4h 45m |
| 2026-06-04 | FDB1687 | ZNZ → DAR | Jun 4, 06:35 UTC | Jun 4, 06:55 UTC | 20m |
| 2026-06-03 | FDB1808 | TLV → DXB | Jun 3, 18:05 UTC | Jun 3, 20:40 UTC | 2h 35m |
| 2026-06-03 | FDB1134 | KTM → DXB | Jun 3, 03:50 UTC | Jun 3, 16:15 UTC | 12h 25m |
| 2026-06-02 | FDB1574 | BGY → DXB | Jun 2, 12:05 UTC | Jun 3, 02:05 UTC | 14h 0m |
| 2026-06-01 | FDB64C | DXB → BGY | Jun 1, 14:15 UTC | Jun 2, 09:35 UTC | 19h 20m |
| 2026-06-01 | FDB64C | DXB → BGY | Jun 1, 12:15 UTC | Jun 2, 09:35 UTC | 21h 20m |
| 2026-05-31 | FDB3PL | DXB → OTP | May 31, 18:05 UTC | Jun 1, 10:30 UTC | 16h 25m |
| 2026-05-31 | FDB3PL | DXB → OTP | May 31, 10:45 UTC | Jun 1, 09:45 UTC | 23h 0m |
| 2026-05-30 | FDB1550 | TLV → DXB | May 30, 08:20 UTC | May 30, 10:55 UTC | 2h 35m |
| 2026-05-29 | FDB2RG | OTP → DXB | May 29, 12:55 UTC | May 30, 06:55 UTC | 18h 0m |
| 2026-05-28 | FDB454 | COK → DXB | May 28, 20:55 UTC | May 29, 07:30 UTC | 10h 35m |
| 2026-05-28 | FDB848 | RUH → DXB | May 28, 07:20 UTC | May 28, 19:15 UTC | 11h 55m |
| 2026-05-27 | FDB446 | BOM → DXB | May 27, 00:14 UTC | May 27, 00:49 UTC | 35m |
| 2026-05-26 | FDB2RG | OTP → DXB | May 26, 12:14 UTC | May 26, 22:50 UTC | 10h 35m |
| 2026-05-26 | FDB3PL | DXB → OTP | May 26, 10:14 UTC | May 26, 10:25 UTC | 10m |
| 2026-05-25 | FDB1212 | TLV → DXB | May 25, 11:05 UTC | May 25, 23:35 UTC | 12h 30m |
| 2026-05-24 | FDB1211 | DXB → TLV | May 24, 23:00 UTC | May 25, 09:25 UTC | 10h 25m |
| 2026-05-24 | FDB746 | TIA → DXB | May 24, 11:25 UTC | May 24, 21:25 UTC | 10h 0m |
| 2026-05-24 | FDB34Q | DXB → TIA | May 24, 08:20 UTC | May 24, 09:25 UTC | 1h 5m |
| 2026-05-22 | FDB2MF | IST → DXB | May 22, 17:05 UTC | May 22, 21:20 UTC | 4h 15m |
| 2026-05-22 | FDB4GP | DXB → IST | May 22, 15:00 UTC | May 22, 15:10 UTC | 10m |
| 2026-05-21 | FDB4GP | DXB → IST | May 21, 20:30 UTC | May 22, 11:50 UTC | 15h 20m |
| 2026-05-20 | FDB5GE | OTP → DXB | May 20, 06:45 UTC | May 20, 10:55 UTC | 4h 10m |
| 2026-05-20 | FDB1NU | DXB → OTP | May 20, 04:45 UTC | May 20, 05:00 UTC | 15m |
| 2026-05-19 | FDB882 | TUU → DXB | May 19, 12:15 UTC | May 20, 02:35 UTC | 14h 20m |
| 2026-05-19 | FDB444 | LKO → DXB | May 19, 03:50 UTC | May 20, 02:35 UTC | 22h 45m |
| 2026-05-18 | FDB443 | DXB → LKO | May 18, 09:35 UTC | May 19, 01:10 UTC | 15h 34m |
| 2026-05-17 | FDB3HP | BSR → DXB | May 17, 16:20 UTC | May 18, 15:40 UTC | 23h 20m |
| 2026-05-17 | FDB2RG | OTP → DXB | May 17, 14:20 UTC | May 18, 09:35 UTC | 19h 15m |
| 2026-05-17 | FDB2RG | OTP → DXB | May 17, 13:05 UTC | May 18, 09:35 UTC | 20h 30m |
| 2026-05-17 | FDB3PL | DXB → OTP | May 17, 10:45 UTC | May 17, 11:25 UTC | 40m |
| 2026-05-15 | FDB570 | CMB → DXB | May 15, 21:10 UTC | May 16, 12:21 UTC | 15h 11m |
| 2026-05-15 | FDB1134 | KTM → DXB | May 15, 03:30 UTC | May 15, 18:55 UTC | 15h 24m |
| 2026-05-14 | FDB1133 | DXB → KTM | May 14, 11:35 UTC | May 15, 01:15 UTC | 13h 40m |
| 2026-05-13 | FDB834 | JED → DXB | May 13, 12:25 UTC | May 14, 11:45 UTC | 23h 20m |
| 2026-05-12 | FDB7KL | AMM → DXB | May 12, 21:25 UTC | May 13, 12:35 UTC | 15h 10m |
| 2026-05-12 | FDB7KL | AMM → DXB | May 12, 15:50 UTC | May 13, 12:35 UTC | 20h 45m |
| 2026-05-12 | FDB7KL | AMM → DXB | May 12, 07:55 UTC | May 13, 07:45 UTC | 23h 50m |
| 2026-05-11 | FDB733 | DXB → GYD | May 11, 15:30 UTC | May 12, 08:25 UTC | 16h 56m |
| 2026-05-10 | FDB71T | TBS → DXB | May 10, 15:55 UTC | May 11, 15:45 UTC | 23h 50m |
| 2026-05-10 | FDB71T | TBS → DXB | May 10, 12:44 UTC | May 10, 16:30 UTC | 3h 45m |
| 2026-05-10 | FDB2WK | DXB → TBS | May 10, 10:10 UTC | May 10, 10:40 UTC | 30m |
| 2026-05-07 | FDB2RG | OTP → DXB | May 7, 13:35 UTC | May 7, 17:55 UTC | 4h 20m |
| 2026-05-07 | FDB3PL | DXB → OTP | May 7, 11:25 UTC | May 7, 12:15 UTC | 50m |
| 2026-05-05 | FDB4CE | BEG → DXB | May 5, 22:35 UTC | May 6, 03:35 UTC | 5h 0m |
| 2026-05-05 | FDB14Q | DXB → BEG | May 5, 18:05 UTC | May 5, 21:05 UTC | 3h 0m |
| 2026-05-04 | FDB2FL | DXB → BGW | May 4, 05:25 UTC | May 4, 13:05 UTC | 7h 40m |
| 2026-05-03 | FDB7MN | OVB → DXB | May 3, 18:30 UTC | May 3, 18:55 UTC | 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-FMH page for operator, model, and routing details .