sensors Mode-S transponder
AE57AE
ICAO 24-bit transponder address
Currently assigned to 14-20702 · SIKORSKY UH-60 Black Hawk
- Hex
- AE57AE
- Octal
- 53453656
- Decimal
- 11,425,710
- Tail
- 14-20702
- Type
- H60
- Flights observed
- 30
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- Jul 21, 04:10 UTC
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| R20702 | - | 30 | 2026-07-21 |
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | R20702 | - | Jul 21, 02:45 UTC | Jul 21, 04:10 UTC | 1h 25m |
| 2026-07-20 | R20702 | HOP → HOP | Jul 20, 23:40 UTC | Jul 21, 01:15 UTC | 1h 35m |
| 2026-06-30 | R20702 | - | Jun 30, 00:04 UTC | Jun 30, 02:40 UTC | 2h 35m |
| 2026-06-29 | R20702 | - | Jun 29, 22:59 UTC | Jun 30, 00:00 UTC | 1h 0m |
| 2026-06-16 | R20702 | HOP → HOP | Jun 16, 02:24 UTC | Jun 16, 04:45 UTC | 2h 20m |
| 2026-06-15 | R20702 | - | Jun 15, 22:45 UTC | Jun 16, 00:40 UTC | 1h 55m |
| 2026-06-12 | R20702 | - | Jun 12, 17:50 UTC | Jun 12, 18:45 UTC | 55m |
| 2026-06-10 | R20702 | HOP → HOP | Jun 10, 02:05 UTC | Jun 10, 04:00 UTC | 1h 55m |
| 2026-06-10 | R20702 | - | Jun 10, 00:40 UTC | Jun 10, 01:35 UTC | 55m |
| 2026-06-08 | R20702 | HOP → HOP | Jun 8, 22:40 UTC | Jun 9, 01:20 UTC | 2h 40m |
| 2026-06-04 | R20702 | - | Jun 4, 22:45 UTC | Jun 4, 23:35 UTC | 50m |
| 2026-06-04 | R20702 | - | Jun 4, 01:55 UTC | Jun 4, 02:35 UTC | 40m |
| 2026-06-03 | R20702 | - | Jun 3, 23:05 UTC | Jun 4, 00:45 UTC | 1h 40m |
| 2026-06-01 | R20702 | - | Jun 1, 19:15 UTC | Jun 1, 21:25 UTC | 2h 10m |
| 2026-06-01 | R20702 | - | Jun 1, 18:25 UTC | Jun 1, 19:10 UTC | 45m |
| 2026-05-29 | R20702 | - | May 29, 02:40 UTC | May 29, 04:20 UTC | 1h 40m |
| 2026-05-29 | R20702 | - | May 29, 00:35 UTC | May 29, 00:45 UTC | 10m |
| 2026-05-28 | R20702 | - | May 28, 23:15 UTC | May 29, 00:00 UTC | 45m |
| 2026-05-28 | R20702 | - | May 28, 22:25 UTC | May 28, 22:40 UTC | 15m |
| 2026-05-27 | R20702 | - | May 27, 02:09 UTC | May 27, 02:59 UTC | 50m |
| 2026-05-26 | R20702 | - | May 26, 22:25 UTC | May 27, 00:34 UTC | 2h 10m |
| 2026-05-15 | R20702 | - | May 15, 02:15 UTC | May 15, 02:55 UTC | 40m |
| 2026-05-14 | R20702 | - | May 14, 22:55 UTC | May 15, 00:40 UTC | 1h 45m |
| 2026-05-06 | R20702 | - | May 6, 20:45 UTC | May 6, 20:55 UTC | 10m |
| 2026-05-01 | R20702 | - | May 1, 19:25 UTC | May 1, 19:35 UTC | 10m |
| 2026-04-28 | R20702 | - | Apr 28, 16:20 UTC | Apr 28, 18:05 UTC | 1h 45m |
| 2026-04-28 | R20702 | - | Apr 28, 15:20 UTC | Apr 28, 15:45 UTC | 25m |
| 2026-04-27 | R20702 | HOP → HOP | Apr 27, 21:20 UTC | Apr 27, 22:45 UTC | 1h 25m |
| 2026-04-14 | R20702 | - | Apr 14, 14:00 UTC | Apr 14, 14:15 UTC | 15m |
| 2026-04-13 | R20702 | HOP → HOP | Apr 13, 21:10 UTC | Apr 13, 21:55 UTC | 45m |
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 14-20702 page for operator, model, and routing details .