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