sensors Mode-S transponder
AE6A76
ICAO 24-bit transponder address
Currently assigned to 20-21136 · Sikorsky UH-60M Black Hawk
- Hex
- AE6A76
- Octal
- 53465166
- Decimal
- 11,430,518
- Tail
- 20-21136
- Type
- H60
- Flights observed
- 45
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- Jul 24, 04:25 UTC
Last known position
Callsign history 2 distinct
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | KYOTE37 | - | Jul 24, 02:05 UTC | Jul 24, 04:20 UTC | 2h 15m |
| 2026-07-23 | KYOTE37 | - | Jul 23, 20:25 UTC | Jul 23, 20:55 UTC | 30m |
| 2026-07-23 | KYOTE36 | - | Jul 23, 15:10 UTC | Jul 23, 15:35 UTC | 25m |
| 2026-07-21 | KYOTE36 | - | Jul 21, 17:45 UTC | Jul 21, 20:00 UTC | 2h 15m |
| 2026-07-17 | KYOTE36 | - | Jul 17, 02:20 UTC | Jul 17, 03:20 UTC | 1h 0m |
| 2026-07-16 | KYOTE36 | - | Jul 16, 17:45 UTC | Jul 16, 19:14 UTC | 1h 30m |
| 2026-07-16 | KYOTE36 | - | Jul 16, 03:30 UTC | Jul 16, 05:20 UTC | 1h 50m |
| 2026-07-15 | KYOTE36 | - | Jul 15, 18:00 UTC | Jul 15, 19:55 UTC | 1h 55m |
| 2026-07-15 | KYOTE36 | - | Jul 15, 04:25 UTC | Jul 15, 04:55 UTC | 30m |
| 2026-07-15 | KYOTE36 | - | Jul 15, 03:00 UTC | Jul 15, 04:20 UTC | 1h 20m |
| 2026-07-14 | KYOTE36 | - | Jul 14, 21:20 UTC | Jul 14, 23:10 UTC | 1h 49m |
| 2026-07-10 | KYOTE36 | - | Jul 10, 20:35 UTC | Jul 10, 21:35 UTC | 1h 0m |
| 2026-07-08 | KYOTE36 | - | Jul 8, 03:30 UTC | Jul 8, 04:30 UTC | 1h 0m |
| 2026-07-08 | KYOTE36 | - | Jul 8, 03:10 UTC | Jul 8, 03:25 UTC | 15m |
| 2026-07-08 | KYOTE36 | - | Jul 8, 02:40 UTC | Jul 8, 02:55 UTC | 15m |
| 2026-07-03 | KYOTE36 | - | Jul 3, 03:00 UTC | Jul 3, 04:45 UTC | 1h 45m |
| 2026-07-03 | KYOTE36 | - | Jul 3, 02:30 UTC | Jul 3, 02:55 UTC | 25m |
| 2026-07-02 | KYOTE36 | - | Jul 2, 04:40 UTC | Jul 2, 05:15 UTC | 35m |
| 2026-07-02 | KYOTE36 | - | Jul 2, 03:25 UTC | Jul 2, 04:05 UTC | 40m |
| 2026-07-01 | KYOTE36 | - | Jul 1, 01:40 UTC | Jul 1, 01:55 UTC | 15m |
| 2026-07-01 | KYOTE36 | - | Jul 1, 00:00 UTC | Jul 1, 01:00 UTC | 1h 0m |
| 2026-06-26 | KYOTE36 | - | Jun 26, 00:24 UTC | Jun 26, 02:09 UTC | 1h 45m |
| 2026-06-18 | KYOTE36 | - | Jun 18, 23:40 UTC | Jun 19, 01:19 UTC | 1h 39m |
| 2026-06-11 | KYOTE36 | - | Jun 11, 02:55 UTC | Jun 11, 04:05 UTC | 1h 10m |
| 2026-06-11 | KYOTE36 | - | Jun 11, 01:55 UTC | Jun 11, 02:25 UTC | 30m |
| 2026-06-10 | KYOTE36 | - | Jun 10, 21:45 UTC | Jun 10, 22:00 UTC | 15m |
| 2026-06-09 | KYOTE36 | - | Jun 9, 02:55 UTC | Jun 9, 03:00 UTC | 5m |
| 2026-06-09 | KYOTE36 | - | Jun 9, 00:20 UTC | Jun 9, 01:45 UTC | 1h 25m |
| 2026-06-08 | KYOTE36 | - | Jun 8, 02:50 UTC | Jun 8, 03:45 UTC | 55m |
| 2026-06-03 | KYOTE36 | - | Jun 3, 14:50 UTC | Jun 3, 17:00 UTC | 2h 10m |
| 2026-05-30 | KYOTE36 | - | May 30, 03:00 UTC | May 30, 03:50 UTC | 50m |
| 2026-05-30 | KYOTE36 | - | May 30, 02:10 UTC | May 30, 02:55 UTC | 45m |
| 2026-05-30 | KYOTE36 | - | May 30, 01:35 UTC | May 30, 02:06 UTC | 31m |
| 2026-05-28 | KYOTE36 | - | May 28, 02:15 UTC | May 28, 04:20 UTC | 2h 5m |
| 2026-05-22 | KYOTE36 | - | May 22, 03:45 UTC | May 22, 04:05 UTC | 20m |
| 2026-05-22 | KYOTE36 | - | May 22, 02:40 UTC | May 22, 03:40 UTC | 1h 0m |
| 2026-05-13 | KYOTE36 | - | May 13, 02:50 UTC | May 13, 04:40 UTC | 1h 50m |
| 2026-05-08 | KYOTE36 | - | May 8, 17:25 UTC | May 8, 18:00 UTC | 35m |
| 2026-05-06 | KYOTE36 | - | May 6, 02:25 UTC | May 6, 03:50 UTC | 1h 25m |
| 2026-05-05 | KYOTE36 | - | May 5, 20:50 UTC | May 5, 21:15 UTC | 25m |
| 2026-05-05 | KYOTE36 | - | May 5, 16:30 UTC | May 5, 16:45 UTC | 15m |
| 2026-04-29 | KYOTE36 | - | Apr 29, 18:40 UTC | Apr 29, 19:00 UTC | 20m |
| 2026-04-29 | KYOTE36 | - | Apr 29, 17:01 UTC | Apr 29, 17:20 UTC | 20m |
| 2026-04-23 | KYOTE36 | - | Apr 23, 02:15 UTC | Apr 23, 04:05 UTC | 1h 50m |
| 2026-04-22 | KYOTE36 | - | Apr 22, 20:10 UTC | Apr 22, 21:45 UTC | 1h 35m |
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 20-21136 page for operator, model, and routing details .