sensors Mode-S transponder
896723
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-FAM · BOMBARDIER CL-600 Challenger
- Hex
- 896723
- Octal
- 42263443
- Decimal
- 9,004,835
- Country
- AE
- Tail
- A6-FAM
- Type
- CL60
- Flights observed
- 64
- Distinct callsigns
- 1
- Country
- AE
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 896723 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| A6FAM | - | 64 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | A6FAM | - | Jul 11, 15:05 UTC | Jul 11, 16:00 UTC | 55m |
| 2026-07-11 | A6FAM | - | Jul 11, 14:15 UTC | Jul 11, 14:30 UTC | 15m |
| 2026-07-07 | A6FAM | - | Jul 7, 14:35 UTC | Jul 7, 18:15 UTC | 3h 40m |
| 2026-07-07 | A6FAM | - | Jul 7, 09:45 UTC | Jul 7, 13:30 UTC | 3h 45m |
| 2026-07-06 | A6FAM | - | Jul 6, 06:25 UTC | Jul 6, 12:55 UTC | 6h 30m |
| 2026-07-05 | A6FAM | - | Jul 5, 23:20 UTC | Jul 6, 04:40 UTC | 5h 20m |
| 2026-07-05 | A6FAM | - | Jul 5, 21:30 UTC | Jul 5, 23:15 UTC | 1h 45m |
| 2026-07-04 | A6FAM | - | Jul 4, 11:40 UTC | Jul 4, 19:00 UTC | 7h 20m |
| 2026-07-04 | A6FAM | - | Jul 4, 08:05 UTC | Jul 4, 10:15 UTC | 2h 10m |
| 2026-07-03 | A6FAM | - | Jul 3, 08:40 UTC | Jul 3, 15:25 UTC | 6h 45m |
| 2026-07-02 | A6FAM | - | Jul 2, 17:45 UTC | Jul 2, 18:05 UTC | 20m |
| 2026-07-01 | A6FAM | - | Jul 1, 12:35 UTC | Jul 1, 14:40 UTC | 2h 5m |
| 2026-06-28 | A6FAM | - | Jun 28, 09:39 UTC | Jun 28, 15:34 UTC | 5h 55m |
| 2026-06-27 | A6FAM | - | Jun 27, 09:29 UTC | Jun 27, 15:45 UTC | 6h 15m |
| 2026-06-27 | A6FAM | - | Jun 27, 09:00 UTC | Jun 27, 09:24 UTC | 25m |
| 2026-06-27 | A6FAM | - | Jun 27, 02:35 UTC | Jun 27, 05:25 UTC | 2h 50m |
| 2026-06-26 | A6FAM | - | Jun 26, 22:05 UTC | Jun 27, 01:04 UTC | 3h 0m |
| 2026-06-19 | A6FAM | - | Jun 19, 15:09 UTC | Jun 19, 15:19 UTC | 10m |
| 2026-06-19 | A6FAM | - | Jun 19, 13:20 UTC | Jun 19, 13:39 UTC | 20m |
| 2026-06-19 | A6FAM | - | Jun 19, 06:29 UTC | Jun 19, 06:49 UTC | 20m |
| 2026-06-16 | A6FAM | DWC → DWC | Jun 16, 09:20 UTC | Jun 16, 09:30 UTC | 10m |
| 2026-06-10 | A6FAM | - | Jun 10, 21:20 UTC | Jun 11, 00:50 UTC | 3h 30m |
| 2026-06-10 | A6FAM | - | Jun 10, 16:05 UTC | Jun 10, 19:30 UTC | 3h 25m |
| 2026-06-05 | A6FAM | - | Jun 5, 03:25 UTC | Jun 5, 09:45 UTC | 6h 20m |
| 2026-06-04 | A6FAM | BOS → BRU | Jun 4, 20:00 UTC | Jun 5, 02:15 UTC | 6h 15m |
| 2026-06-04 | A6FAM | - | Jun 4, 15:40 UTC | Jun 4, 19:05 UTC | 3h 25m |
| 2026-06-03 | A6FAM | - | Jun 3, 19:45 UTC | Jun 3, 22:35 UTC | 2h 50m |
| 2026-06-02 | A6FAM | BRU → YHM | Jun 2, 10:40 UTC | Jun 2, 18:20 UTC | 7h 40m |
| 2026-05-30 | A6FAM | - | May 30, 11:55 UTC | May 30, 16:15 UTC | 4h 20m |
| 2026-05-30 | A6FAM | - | May 30, 10:05 UTC | May 30, 10:20 UTC | 15m |
| 2026-05-25 | A6FAM | - | May 25, 19:05 UTC | May 25, 19:15 UTC | 10m |
| 2026-05-24 | A6FAM | - | May 24, 19:25 UTC | May 24, 20:50 UTC | 1h 25m |
| 2026-05-24 | A6FAM | - | May 24, 16:20 UTC | May 24, 18:00 UTC | 1h 40m |
| 2026-05-23 | A6FAM | - | May 23, 01:35 UTC | May 23, 01:45 UTC | 10m |
| 2026-05-19 | A6FAM | - | May 19, 23:30 UTC | May 20, 01:50 UTC | 2h 20m |
| 2026-05-19 | A6FAM | - | May 19, 20:35 UTC | May 19, 21:40 UTC | 1h 5m |
| 2026-05-18 | A6FAM | - | May 18, 13:35 UTC | May 18, 13:45 UTC | 10m |
| 2026-05-18 | A6FAM | - | May 18, 11:15 UTC | May 18, 11:30 UTC | 15m |
| 2026-05-15 | A6FAM | - | May 15, 08:35 UTC | May 15, 08:55 UTC | 20m |
| 2026-05-02 | A6FAM | - | May 2, 04:20 UTC | May 2, 07:15 UTC | 2h 55m |
| 2026-05-01 | A6FAM | - | May 1, 08:25 UTC | May 1, 11:55 UTC | 3h 30m |
| 2026-04-30 | A6FAM | - | Apr 30, 18:10 UTC | Apr 30, 18:30 UTC | 20m |
| 2026-04-28 | A6FAM | - | Apr 28, 12:50 UTC | Apr 28, 13:00 UTC | 10m |
| 2026-04-25 | A6FAM | - | Apr 25, 02:35 UTC | Apr 25, 09:15 UTC | 6h 40m |
| 2026-04-24 | A6FAM | - | Apr 24, 16:05 UTC | Apr 24, 23:50 UTC | 7h 45m |
| 2026-04-23 | A6FAM | - | Apr 23, 03:30 UTC | Apr 23, 10:35 UTC | 7h 5m |
| 2026-04-22 | A6FAM | - | Apr 22, 20:30 UTC | Apr 23, 02:20 UTC | 5h 50m |
| 2026-04-22 | A6FAM | - | Apr 22, 13:05 UTC | Apr 22, 18:35 UTC | 5h 30m |
| 2026-04-22 | A6FAM | - | Apr 22, 07:30 UTC | Apr 22, 11:15 UTC | 3h 45m |
| 2026-04-20 | A6FAM | - | Apr 20, 18:20 UTC | Apr 20, 21:15 UTC | 2h 55m |
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-FAM page for operator, model, and routing details .