sensors Mode-S transponder
89646B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FGD · BOEING 737-800
- Hex
- 89646B
- Octal
- 42262153
- Decimal
- 9,004,139
- Country
- AE
- Tail
- A6-FGD
- Type
- B738
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 89646B 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 |
|---|---|---|---|
| FDB867 | Fly Dubai | 3 | 2026-05-01 |
| FDB868 | Fly Dubai | 2 | 2026-05-01 |
| FDB856 | Fly Dubai | 2 | 2026-05-09 |
| FDB848 | Fly Dubai | 2 | 2026-04-16 |
| FDB7ZK | Fly Dubai | 2 | 2026-04-28 |
| FDB3YK | Fly Dubai | 2 | 2026-04-28 |
| FDB3UF | Fly Dubai | 2 | 2026-05-05 |
| FDB3HP | Fly Dubai | 2 | 2026-05-30 |
| FDB15L | Fly Dubai | 2 | 2026-04-19 |
| FDB1 | Fly Dubai | 2 | 2026-05-06 |
| FDB9RQ | Fly Dubai | 1 | 2026-05-04 |
| FDB9342 | - | 1 | 2026-05-29 |
| FDB9341 | - | 1 | 2026-05-25 |
| FDB847 | Fly Dubai | 1 | 2026-04-16 |
| FDB7HD | Fly Dubai | 1 | 2026-05-02 |
| FDB7AF | Fly Dubai | 1 | 2026-05-31 |
| FDB75L | Fly Dubai | 1 | 2026-04-19 |
| FDB5WB | Fly Dubai | 1 | 2026-05-22 |
| FDB4YF | Fly Dubai | 1 | 2026-05-23 |
| FDB1ZA | Fly Dubai | 1 | 2026-05-22 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | FDB7AF | DEL → DXB | May 31, 22:40 UTC | May 31, 23:10 UTC | 30m |
| 2026-05-31 | FDB1082 | TLV → DXB | May 31, 13:15 UTC | May 31, 21:25 UTC | 8h 10m |
| 2026-05-31 | FDB1081 | DXB → TLV | May 31, 11:20 UTC | May 31, 11:55 UTC | 35m |
| 2026-05-30 | FDB3HP | BSR → DXB | May 30, 14:50 UTC | May 31, 11:55 UTC | 21h 5m |
| 2026-05-29 | FDB3HP | BSR → DXB | May 29, 20:50 UTC | May 30, 15:30 UTC | 18h 40m |
| 2026-05-29 | FDB9342 | - | May 29, 19:45 UTC | May 29, 21:00 UTC | 1h 15m |
| 2026-05-25 | FDB9341 | - | May 25, 15:30 UTC | May 25, 16:45 UTC | 1h 15m |
| 2026-05-23 | FDB4YF | SAW → DXB | May 23, 13:00 UTC | May 23, 16:30 UTC | 3h 30m |
| 2026-05-22 | FDB1ZA | SPX → DXB | May 22, 23:05 UTC | May 23, 02:15 UTC | 3h 10m |
| 2026-05-22 | FDB5WB | BEY → DXB | May 22, 14:05 UTC | May 22, 14:45 UTC | 40m |
| 2026-05-21 | FDB16T | BAH → DXB | May 21, 14:30 UTC | May 21, 15:25 UTC | 55m |
| 2026-05-09 | FDB856 | RUH → DXB | May 9, 20:10 UTC | May 9, 20:20 UTC | 10m |
| 2026-05-09 | FDB856 | RUH → DXB | May 9, 18:50 UTC | May 9, 19:30 UTC | 40m |
| 2026-05-06 | FDB1 | DXB → DOH | May 6, 06:45 UTC | May 6, 07:20 UTC | 35m |
| 2026-05-05 | FDB3UF | MCT → DXB | May 5, 06:20 UTC | May 5, 06:45 UTC | 25m |
| 2026-05-04 | FDB9RQ | DOH → DXB | May 4, 07:20 UTC | May 4, 08:05 UTC | 45m |
| 2026-05-04 | FDB1 | DXB → DOH | May 4, 05:00 UTC | May 4, 05:40 UTC | 40m |
| 2026-05-02 | FDB3UF | MCT → DXB | May 2, 05:25 UTC | May 2, 06:00 UTC | 35m |
| 2026-05-02 | FDB7HD | DXB → MCT | May 2, 03:25 UTC | May 2, 03:45 UTC | 20m |
| 2026-05-01 | FDB868 | DMM → DXB | May 1, 16:55 UTC | May 1, 17:50 UTC | 55m |
| 2026-05-01 | FDB867 | DXB → DMM | May 1, 14:25 UTC | May 1, 15:20 UTC | 55m |
| 2026-04-28 | FDB7ZK | DOH → DXB | Apr 28, 15:50 UTC | Apr 28, 16:25 UTC | 35m |
| 2026-04-28 | FDB3YK | DXB → DOH | Apr 28, 13:15 UTC | Apr 28, 14:15 UTC | 1h 0m |
| 2026-04-23 | FDB7ZK | DOH → DXB | Apr 23, 16:40 UTC | Apr 23, 17:55 UTC | 1h 14m |
| 2026-04-23 | FDB3YK | DXB → DOH | Apr 23, 13:45 UTC | Apr 23, 15:10 UTC | 1h 25m |
| 2026-04-19 | FDB75L | BAH → DXB | Apr 19, 13:00 UTC | Apr 19, 15:05 UTC | 2h 5m |
| 2026-04-19 | FDB15L | DXB → BAH | Apr 19, 11:25 UTC | Apr 19, 11:35 UTC | 10m |
| 2026-04-19 | FDB15L | DXB → BAH | Apr 19, 09:20 UTC | Apr 19, 10:30 UTC | 1h 10m |
| 2026-04-16 | FDB848 | RUH → DXB | Apr 16, 09:10 UTC | Apr 16, 09:29 UTC | 20m |
| 2026-04-16 | FDB848 | RUH → DXB | Apr 16, 08:09 UTC | Apr 16, 09:05 UTC | 55m |
| 2026-04-16 | FDB847 | DXB → RUH | Apr 16, 03:55 UTC | Apr 16, 05:05 UTC | 1h 10m |
| 2026-04-14 | FDB868 | DMM → DXB | Apr 14, 17:25 UTC | Apr 14, 18:45 UTC | 1h 20m |
| 2026-04-14 | FDB867 | DXB → DMM | Apr 14, 14:50 UTC | Apr 14, 15:00 UTC | 10m |
| 2026-04-14 | FDB867 | DXB → DMM | Apr 14, 13:15 UTC | Apr 14, 14:45 UTC | 1h 30m |
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-FGD page for operator, model, and routing details .