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