sensors Mode-S transponder
89646A
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FGC · BOEING 737-800
- Hex
- 89646A
- Octal
- 42262152
- Decimal
- 9,004,138
- Country
- AE
- Tail
- A6-FGC
- Type
- B738
- Flights observed
- 52
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- Jul 26, 17:10 UTC
Current position
Country allocation
The ICAO 24-bit address 89646A 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 |
|---|---|---|---|
| FDB143 | Fly Dubai | 3 | 2026-06-08 |
| FDB9341 | - | 2 | 2026-04-23 |
| FDB7XZ | Fly Dubai | 2 | 2026-05-23 |
| FDB7KL | Fly Dubai | 2 | 2026-06-07 |
| FDB725 | Fly Dubai | 2 | 2026-07-26 |
| FDB5JA | - | 2 | 2026-07-20 |
| FDB441 | - | 2 | 2026-07-21 |
| FDB1YT | Fly Dubai | 2 | 2026-05-22 |
| FDB9RF | Fly Dubai | 1 | 2026-05-24 |
| FDB94F | Fly Dubai | 1 | 2026-04-18 |
| FDB9002 | - | 1 | 2026-07-16 |
| FDB876 | Fly Dubai | 1 | 2026-07-20 |
| FDB872 | - | 1 | 2026-05-29 |
| FDB868 | Fly Dubai | 1 | 2026-06-03 |
| FDB830 | Fly Dubai | 1 | 2026-07-18 |
| FDB812 | Fly Dubai | 1 | 2026-04-13 |
| FDB811 | Fly Dubai | 1 | 2026-04-13 |
| FDB7WA | Fly Dubai | 1 | 2026-04-22 |
| FDB7AF | Fly Dubai | 1 | 2026-07-21 |
| FDB756 | Fly Dubai | 1 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FDB2TM | BUS → DXB | Jul 26, 13:20 UTC | Jul 26, 17:10 UTC | 3h 50m |
| 2026-07-26 | FDB725 | DXB → BUS | Jul 26, 11:25 UTC | Jul 26, 11:35 UTC | 10m |
| 2026-07-26 | FDB725 | DXB → BUS | Jul 26, 08:30 UTC | Jul 26, 09:10 UTC | 40m |
| 2026-07-25 | FDB1ND | GYD → DXB | Jul 25, 11:40 UTC | Jul 25, 18:50 UTC | 7h 10m |
| 2026-07-24 | FDB756 | IST → DXB | Jul 24, 23:55 UTC | Jul 25, 04:05 UTC | 4h 10m |
| 2026-07-24 | FDB3VG | DXB → IST | Jul 24, 17:00 UTC | Jul 24, 21:30 UTC | 4h 30m |
| 2026-07-24 | FDB2RK | GYD → DXB | Jul 24, 03:15 UTC | Jul 24, 12:55 UTC | 9h 40m |
| 2026-07-21 | FDB7AF | DEL → DXB | Jul 21, 23:35 UTC | Jul 22, 00:05 UTC | 30m |
| 2026-07-21 | FDB441 | - | Jul 21, 20:40 UTC | Jul 21, 21:20 UTC | 40m |
| 2026-07-21 | FDB4YF | SAW → DXB | Jul 21, 11:10 UTC | Jul 21, 15:45 UTC | 4h 35m |
| 2026-07-21 | FDB5KG | DXB → SAW | Jul 21, 04:55 UTC | Jul 21, 08:55 UTC | 4h 0m |
| 2026-07-20 | FDB876 | TIF → DXB | Jul 20, 18:00 UTC | Jul 20, 18:20 UTC | 20m |
| 2026-07-20 | FDB5WB | - | Jul 20, 07:25 UTC | Jul 20, 11:00 UTC | 3h 35m |
| 2026-07-20 | FDB5JA | - | Jul 20, 03:30 UTC | Jul 20, 05:40 UTC | 2h 10m |
| 2026-07-20 | FDB5JA | DXB → DXB | Jul 20, 03:05 UTC | Jul 20, 03:25 UTC | 20m |
| 2026-07-19 | FDB20 | DOH → DXB | Jul 19, 19:50 UTC | Jul 19, 20:15 UTC | 25m |
| 2026-07-19 | FDB2KF | - | Jul 19, 17:30 UTC | Jul 19, 18:10 UTC | 40m |
| 2026-07-19 | FDB618 | JIB → DXB | Jul 19, 15:00 UTC | Jul 19, 15:30 UTC | 30m |
| 2026-07-18 | FDB830 | JED → DXB | Jul 18, 04:30 UTC | Jul 18, 18:20 UTC | 13h 50m |
| 2026-07-17 | FDB651 | DXB → DXB | Jul 17, 10:20 UTC | Jul 17, 10:50 UTC | 30m |
| 2026-07-17 | FDB1134 | - | Jul 17, 05:04 UTC | Jul 17, 05:35 UTC | 30m |
| 2026-07-16 | FDB1133 | - | Jul 16, 22:30 UTC | Jul 17, 01:45 UTC | 3h 15m |
| 2026-07-16 | FDB1125 | - | Jul 16, 10:04 UTC | Jul 16, 13:05 UTC | 3h 0m |
| 2026-07-16 | FDB9002 | - | Jul 16, 06:45 UTC | Jul 16, 07:00 UTC | 15m |
| 2026-06-10 | FDB2MF | IST → DXB | Jun 10, 15:50 UTC | Jun 11, 10:25 UTC | 18h 35m |
| 2026-06-10 | FDB4GP | DXB → IST | Jun 10, 13:30 UTC | Jun 10, 14:10 UTC | 40m |
| 2026-06-08 | FDB143 | DXB → AMM | Jun 8, 16:05 UTC | Jun 8, 16:15 UTC | 10m |
| 2026-06-07 | FDB7KL | AMM → DXB | Jun 7, 20:15 UTC | Jun 7, 20:25 UTC | 10m |
| 2026-06-07 | FDB143 | DXB → AMM | Jun 7, 18:10 UTC | Jun 7, 18:30 UTC | 20m |
| 2026-06-05 | FDB5YM | DOH → DXB | Jun 5, 14:20 UTC | Jun 5, 15:00 UTC | 40m |
| 2026-06-04 | FDB7KL | AMM → DXB | Jun 4, 19:35 UTC | Jun 4, 22:15 UTC | 2h 40m |
| 2026-06-04 | FDB143 | DXB → AMM | Jun 4, 17:55 UTC | Jun 4, 18:15 UTC | 20m |
| 2026-06-03 | FDB868 | DMM → DXB | Jun 3, 17:00 UTC | Jun 3, 18:05 UTC | 1h 5m |
| 2026-06-03 | FDB1549 | DXB → TLV | Jun 3, 04:25 UTC | Jun 3, 07:20 UTC | 2h 55m |
| 2026-06-02 | FDB662 | HGA → DXB | Jun 2, 12:00 UTC | Jun 2, 12:35 UTC | 35m |
| 2026-05-31 | FDB707 | DXB → GYD | May 31, 13:35 UTC | May 31, 14:10 UTC | 35m |
| 2026-05-29 | FDB872 | - | May 29, 12:25 UTC | May 29, 23:45 UTC | 11h 20m |
| 2026-05-24 | FDB454 | COK → DXB | May 24, 23:00 UTC | May 24, 23:10 UTC | 10m |
| 2026-05-24 | FDB9RF | DXB → COK | May 24, 01:05 UTC | May 24, 20:05 UTC | 19h 0m |
| 2026-05-23 | FDB7XZ | BGW → DXB | May 23, 12:00 UTC | May 24, 01:05 UTC | 13h 5m |
| 2026-05-22 | FDB7XZ | BGW → DXB | May 22, 23:40 UTC | May 23, 12:40 UTC | 12h 59m |
| 2026-05-22 | FDB441 | DXB → DEL | May 22, 21:10 UTC | May 22, 21:50 UTC | 40m |
| 2026-05-22 | FDB1YT | BAH → DXB | May 22, 05:40 UTC | May 22, 06:35 UTC | 55m |
| 2026-05-14 | FDB1YT | BAH → DXB | May 14, 06:25 UTC | May 14, 07:20 UTC | 55m |
| 2026-04-23 | FDB9341 | - | Apr 23, 16:30 UTC | Apr 23, 16:50 UTC | 20m |
| 2026-04-23 | FDB9341 | - | Apr 23, 14:25 UTC | Apr 23, 14:50 UTC | 25m |
| 2026-04-22 | FDB7WA | MCT → DXB | Apr 22, 17:15 UTC | Apr 22, 17:35 UTC | 20m |
| 2026-04-22 | FDB3PM | DXB → MCT | Apr 22, 14:50 UTC | Apr 22, 15:10 UTC | 20m |
| 2026-04-18 | FDB5JN | MCT → DXB | Apr 18, 09:40 UTC | Apr 18, 10:10 UTC | 30m |
| 2026-04-18 | FDB94F | DXB → MCT | Apr 18, 07:25 UTC | Apr 18, 07:40 UTC | 15m |
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-FGC page for operator, model, and routing details .