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