sensors Mode-S transponder
AE2FA9
ICAO 24-bit transponder address
Currently assigned to 08-8197 · Boeing C-17A Globemaster III
- Hex
- AE2FA9
- Octal
- 53427651
- Decimal
- 11,415,465
- Tail
- 08-8197
- Type
- C17
- Flights observed
- 24
- Distinct callsigns
- 7
- Country
- -
- Last broadcast
- 9h ago
Last known position
Callsign history 7 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RCH563 | Air Mobility Command | 6 | 2026-06-10 |
| RCH309 | - | 6 | 2026-06-17 |
| RCH797 | Air Mobility Command | 4 | 2026-05-29 |
| SOUND35 | - | 3 | 2026-07-14 |
| RCH1866 | - | 3 | 2026-05-21 |
| RCH553 | - | 1 | 2026-07-03 |
| RCH542 | Air Mobility Command | 1 | 2026-05-02 |
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SOUND35 | - | Jul 14, 05:05 UTC | Jul 14, 06:25 UTC | 1h 20m |
| 2026-07-14 | SOUND35 | - | Jul 14, 03:45 UTC | Jul 14, 04:10 UTC | 25m |
| 2026-07-14 | SOUND35 | - | Jul 14, 00:55 UTC | Jul 14, 02:45 UTC | 1h 50m |
| 2026-07-03 | RCH553 | - | Jul 3, 01:55 UTC | Jul 3, 09:05 UTC | 7h 10m |
| 2026-06-17 | RCH309 | OKO → TCM | Jun 17, 06:45 UTC | Jun 17, 15:46 UTC | 9h 0m |
| 2026-06-16 | RCH309 | - | Jun 16, 08:30 UTC | Jun 16, 09:25 UTC | 55m |
| 2026-06-16 | RCH309 | - | Jun 16, 04:50 UTC | Jun 16, 05:50 UTC | 1h 0m |
| 2026-06-15 | RCH309 | - | Jun 15, 11:10 UTC | Jun 15, 11:45 UTC | 35m |
| 2026-06-15 | RCH309 | - | Jun 15, 04:30 UTC | Jun 15, 06:15 UTC | 1h 45m |
| 2026-06-14 | RCH309 | - | Jun 14, 04:45 UTC | Jun 14, 07:50 UTC | 3h 5m |
| 2026-06-10 | RCH563 | PAP → CHS | Jun 10, 17:35 UTC | Jun 10, 20:30 UTC | 2h 55m |
| 2026-06-09 | RCH563 | PAP → CHS | Jun 9, 16:45 UTC | Jun 9, 17:00 UTC | 15m |
| 2026-06-09 | RCH563 | PAP → CHS | Jun 9, 07:50 UTC | Jun 9, 15:50 UTC | 8h 0m |
| 2026-06-09 | RCH563 | PAP → CHS | Jun 9, 03:15 UTC | Jun 9, 04:45 UTC | 1h 30m |
| 2026-06-01 | RCH563 | PAP → CHS | Jun 1, 06:00 UTC | Jun 1, 12:05 UTC | 6h 5m |
| 2026-06-01 | RCH563 | PAP → CHS | Jun 1, 00:35 UTC | Jun 1, 04:00 UTC | 3h 25m |
| 2026-05-29 | RCH797 | SUU → RIV | May 29, 19:40 UTC | May 30, 00:05 UTC | 4h 25m |
| 2026-05-29 | RCH797 | SUU → RIV | May 29, 14:40 UTC | May 29, 17:30 UTC | 2h 50m |
| 2026-05-29 | RCH797 | SUU → RIV | May 29, 06:10 UTC | May 29, 13:35 UTC | 7h 25m |
| 2026-05-28 | RCH797 | SUU → RIV | May 28, 15:45 UTC | May 28, 19:20 UTC | 3h 35m |
| 2026-05-21 | RCH1866 | - | May 21, 07:20 UTC | May 21, 09:25 UTC | 2h 5m |
| 2026-05-20 | RCH1866 | - | May 20, 23:35 UTC | May 21, 03:05 UTC | 3h 30m |
| 2026-05-18 | RCH1866 | - | May 18, 04:45 UTC | May 18, 08:45 UTC | 4h 0m |
| 2026-05-02 | RCH542 | PIK → PIK | May 2, 09:50 UTC | May 2, 12:30 UTC | 2h 40m |
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 08-8197 page for operator, model, and routing details .