sensors Mode-S transponder
AE5CA6
ICAO 24-bit transponder address
Currently assigned to 05-27045 · SIKORSKY UH-60 Black Hawk
- Hex
- AE5CA6
- Octal
- 53456246
- Decimal
- 11,426,982
- Tail
- 05-27045
- Type
- H60
- Flights observed
- 54
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- 10d ago
Last known position
Callsign history 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | JOLLY96 | - | Jul 9, 22:20 UTC | Jul 9, 22:30 UTC | 10m |
| 2026-07-09 | JOLLY96 | - | Jul 9, 21:25 UTC | Jul 9, 21:35 UTC | 10m |
| 2026-07-09 | JOLLY96 | - | Jul 9, 17:45 UTC | Jul 9, 18:40 UTC | 55m |
| 2026-07-09 | JOLLY96 | - | Jul 9, 16:50 UTC | Jul 9, 17:10 UTC | 20m |
| 2026-07-08 | JOLLY96 | - | Jul 8, 21:40 UTC | Jul 8, 22:35 UTC | 55m |
| 2026-07-08 | JOLLY96 | - | Jul 8, 19:40 UTC | Jul 8, 20:05 UTC | 25m |
| 2026-07-07 | JOLLY96 | - | Jul 7, 21:20 UTC | Jul 7, 21:45 UTC | 25m |
| 2026-07-07 | JOLLY96 | - | Jul 7, 17:25 UTC | Jul 7, 18:00 UTC | 35m |
| 2026-07-07 | JOLLY96 | NUQ → NUQ | Jul 7, 17:05 UTC | Jul 7, 17:10 UTC | 5m |
| 2026-07-07 | JOLLY96 | NUQ → NUQ | Jul 7, 16:55 UTC | Jul 7, 17:00 UTC | 5m |
| 2026-06-22 | JOLLY96 | - | Jun 22, 21:59 UTC | Jun 22, 22:59 UTC | 1h 0m |
| 2026-06-22 | JOLLY96 | - | Jun 22, 16:24 UTC | Jun 22, 17:25 UTC | 1h 0m |
| 2026-06-22 | JOLLY96 | NUQ → NUQ | Jun 22, 16:14 UTC | Jun 22, 16:20 UTC | 5m |
| 2026-06-15 | JOLLY96 | - | Jun 15, 22:54 UTC | Jun 15, 23:19 UTC | 25m |
| 2026-06-15 | JOLLY96 | - | Jun 15, 18:04 UTC | Jun 15, 19:00 UTC | 55m |
| 2026-06-15 | JOLLY96 | - | Jun 15, 16:59 UTC | Jun 15, 17:20 UTC | 20m |
| 2026-06-10 | JOLLY96 | - | Jun 10, 23:25 UTC | Jun 10, 23:50 UTC | 25m |
| 2026-06-10 | JOLLY96 | - | Jun 10, 21:15 UTC | Jun 10, 21:25 UTC | 10m |
| 2026-06-10 | JOLLY96 | - | Jun 10, 19:40 UTC | Jun 10, 20:05 UTC | 25m |
| 2026-06-10 | JOLLY96 | - | Jun 10, 15:00 UTC | Jun 10, 16:30 UTC | 1h 30m |
| 2026-06-09 | JOLLY99 | NUQ → NUQ | Jun 9, 21:10 UTC | Jun 9, 21:20 UTC | 10m |
| 2026-06-09 | JOLLY99 | NUQ → NUQ | Jun 9, 20:30 UTC | Jun 9, 21:05 UTC | 35m |
| 2026-06-09 | JOLLY99 | NUQ → NUQ | Jun 9, 19:55 UTC | Jun 9, 20:20 UTC | 25m |
| 2026-06-02 | JOLLY96 | NUQ → NUQ | Jun 2, 22:40 UTC | Jun 2, 23:00 UTC | 20m |
| 2026-06-02 | JOLLY96 | NUQ → NUQ | Jun 2, 22:15 UTC | Jun 2, 22:30 UTC | 15m |
| 2026-06-02 | JOLLY96 | - | Jun 2, 20:20 UTC | Jun 2, 22:00 UTC | 1h 40m |
| 2026-06-02 | JOLLY96 | - | Jun 2, 18:50 UTC | Jun 2, 19:00 UTC | 10m |
| 2026-06-02 | JOLLY96 | - | Jun 2, 18:35 UTC | Jun 2, 18:45 UTC | 10m |
| 2026-06-02 | JOLLY96 | RAL → SBD | Jun 2, 16:45 UTC | Jun 2, 16:55 UTC | 10m |
| 2026-06-01 | JOLLY96 | - | Jun 1, 21:45 UTC | Jun 1, 22:10 UTC | 25m |
| 2026-06-01 | JOLLY96 | - | Jun 1, 18:50 UTC | Jun 1, 19:30 UTC | 40m |
| 2026-06-01 | JOLLY96 | - | Jun 1, 17:40 UTC | Jun 1, 18:20 UTC | 40m |
| 2026-05-13 | JOLLY96 | - | May 13, 21:25 UTC | May 13, 21:50 UTC | 25m |
| 2026-05-13 | JOLLY96 | - | May 13, 20:10 UTC | May 13, 20:50 UTC | 40m |
| 2026-05-13 | JOLLY96 | - | May 13, 19:25 UTC | May 13, 19:35 UTC | 10m |
| 2026-05-13 | JOLLY96 | RAL → RAL | May 13, 16:40 UTC | May 13, 18:25 UTC | 1h 45m |
| 2026-05-12 | JOLLY96 | - | May 12, 22:01 UTC | May 12, 22:10 UTC | 10m |
| 2026-05-12 | JOLLY96 | - | May 12, 21:40 UTC | May 12, 21:50 UTC | 10m |
| 2026-05-12 | JOLLY96 | - | May 12, 17:55 UTC | May 12, 18:15 UTC | 20m |
| 2026-05-11 | JOLLY96 | - | May 11, 17:05 UTC | May 11, 17:30 UTC | 25m |
| 2026-04-22 | JOLLY96 | - | Apr 22, 19:35 UTC | Apr 22, 20:05 UTC | 30m |
| 2026-04-22 | JOLLY96 | - | Apr 22, 18:15 UTC | Apr 22, 18:45 UTC | 30m |
| 2026-04-22 | JOLLY96 | - | Apr 22, 17:30 UTC | Apr 22, 17:40 UTC | 10m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 23:20 UTC | Apr 21, 23:30 UTC | 10m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 22:45 UTC | Apr 21, 23:10 UTC | 25m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 21:10 UTC | Apr 21, 22:10 UTC | 1h 0m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 19:15 UTC | Apr 21, 19:25 UTC | 10m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 18:20 UTC | Apr 21, 18:30 UTC | 10m |
| 2026-04-21 | JOLLY96 | - | Apr 21, 16:31 UTC | Apr 21, 16:35 UTC | 5m |
| 2026-04-20 | JOLLY96 | - | Apr 20, 21:30 UTC | Apr 20, 21:50 UTC | 20m |
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 05-27045 page for operator, model, and routing details .