sensors Mode-S transponder
AE275D
ICAO 24-bit transponder address
Currently assigned to 165778 · SIKORSKY UH-60 Black Hawk
- Hex
- AE275D
- Octal
- 53423535
- Decimal
- 11,413,341
- Tail
- 165778
- Type
- H60
- Flights observed
- 30
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- 2d ago
Last known position
Callsign history 3 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | RDHK705 | - | Jul 15, 17:35 UTC | Jul 15, 18:45 UTC | 1h 10m |
| 2026-07-15 | RDHK705 | - | Jul 15, 15:45 UTC | Jul 15, 17:25 UTC | 1h 40m |
| 2026-07-10 | RDHK705 | - | Jul 10, 18:25 UTC | Jul 10, 19:05 UTC | 40m |
| 2026-07-10 | RDHK705 | - | Jul 10, 16:50 UTC | Jul 10, 17:00 UTC | 10m |
| 2026-07-09 | RDHK705 | - | Jul 9, 02:10 UTC | Jul 9, 04:05 UTC | 1h 55m |
| 2026-07-09 | RDHK705 | - | Jul 9, 01:45 UTC | Jul 9, 02:00 UTC | 15m |
| 2026-07-08 | RDHK705 | - | Jul 8, 23:55 UTC | Jul 9, 00:55 UTC | 1h 0m |
| 2026-07-08 | RDHK705 | - | Jul 8, 20:25 UTC | Jul 8, 23:45 UTC | 3h 20m |
| 2026-07-08 | RDHK705 | - | Jul 8, 19:05 UTC | Jul 8, 19:20 UTC | 15m |
| 2026-07-07 | FFAB123 | - | Jul 7, 17:20 UTC | Jul 7, 18:25 UTC | 1h 5m |
| 2026-07-01 | RDHK705 | - | Jul 1, 14:25 UTC | Jul 1, 14:45 UTC | 20m |
| 2026-07-01 | RDHK705 | - | Jul 1, 13:10 UTC | Jul 1, 13:20 UTC | 10m |
| 2026-06-30 | RDHK705 | - | Jun 30, 20:05 UTC | Jun 30, 21:05 UTC | 1h 0m |
| 2026-06-30 | RDHK705 | - | Jun 30, 18:40 UTC | Jun 30, 19:15 UTC | 35m |
| 2026-06-30 | RDHK705 | - | Jun 30, 17:25 UTC | Jun 30, 18:30 UTC | 1h 5m |
| 2026-06-26 | HAWK705 | - | Jun 26, 18:39 UTC | Jun 26, 19:20 UTC | 40m |
| 2026-06-26 | HAWK705 | - | Jun 26, 17:44 UTC | Jun 26, 17:54 UTC | 10m |
| 2026-06-26 | HAWK705 | - | Jun 26, 16:35 UTC | Jun 26, 17:35 UTC | 1h 0m |
| 2026-06-25 | RDHK705 | NGU → NGU | Jun 25, 19:29 UTC | Jun 25, 20:30 UTC | 1h 0m |
| 2026-06-25 | RDHK705 | - | Jun 25, 16:35 UTC | Jun 25, 17:25 UTC | 50m |
| 2026-06-20 | RDHK705 | - | Jun 20, 18:40 UTC | Jun 20, 19:55 UTC | 1h 15m |
| 2026-04-18 | RDHK705 | - | Apr 18, 03:25 UTC | Apr 18, 03:50 UTC | 25m |
| 2026-04-18 | RDHK705 | - | Apr 18, 01:45 UTC | Apr 18, 02:30 UTC | 45m |
| 2026-04-18 | RDHK705 | - | Apr 18, 01:25 UTC | Apr 18, 01:35 UTC | 10m |
| 2026-04-18 | RDHK705 | - | Apr 18, 01:00 UTC | Apr 18, 01:20 UTC | 20m |
| 2026-04-17 | RDHK705 | - | Apr 17, 23:40 UTC | Apr 17, 23:50 UTC | 10m |
| 2026-04-17 | RDHK705 | - | Apr 17, 22:45 UTC | Apr 17, 23:10 UTC | 25m |
| 2026-04-17 | RDHK705 | - | Apr 17, 19:45 UTC | Apr 17, 21:05 UTC | 1h 20m |
| 2026-04-17 | - | FAF → FAF | Apr 17, 18:50 UTC | Apr 17, 19:05 UTC | 15m |
| 2026-04-17 | RDHK705 | - | Apr 17, 18:00 UTC | Apr 17, 18:10 UTC | 10m |
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 165778 page for operator, model, and routing details .