sensors Mode-S transponder
AE6C7F
ICAO 24-bit transponder address
Currently assigned to 21-21200 · Sikorsky HH-60M Black Hawk
- Hex
- AE6C7F
- Octal
- 53466177
- Decimal
- 11,431,039
- Tail
- 21-21200
- Type
- H60
- Flights observed
- 30
- Distinct callsigns
- 6
- Country
- -
- Last broadcast
- 5d ago
Last known position
Callsign history 6 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | BOREAL2 | - | Jun 17, 21:00 UTC | Jun 17, 22:15 UTC | 1h 15m |
| 2026-06-11 | BOREAL2 | - | Jun 11, 18:35 UTC | Jun 11, 19:10 UTC | 35m |
| 2026-06-08 | BOREAL5 | - | Jun 8, 22:30 UTC | Jun 8, 22:45 UTC | 15m |
| 2026-06-08 | BOREAL5 | - | Jun 8, 21:35 UTC | Jun 8, 22:25 UTC | 50m |
| 2026-06-08 | BOREAL5 | FBK → FBK | Jun 8, 20:30 UTC | Jun 8, 21:20 UTC | 50m |
| 2026-06-04 | LICHEN9 | - | Jun 4, 20:15 UTC | Jun 4, 20:25 UTC | 10m |
| 2026-06-02 | LICHEN6 | FBK → FBK | Jun 2, 23:15 UTC | Jun 2, 23:30 UTC | 15m |
| 2026-06-02 | LICHEN6 | FBK → FBK | Jun 2, 21:35 UTC | Jun 2, 22:55 UTC | 1h 20m |
| 2026-06-02 | LICHEN6 | FBK → FBK | Jun 2, 21:25 UTC | Jun 2, 21:30 UTC | 5m |
| 2026-05-28 | LICHEN6 | FBK → FBK | May 28, 19:05 UTC | May 28, 20:25 UTC | 1h 20m |
| 2026-05-21 | R21200 | FBK → FBK | May 21, 18:50 UTC | May 21, 19:40 UTC | 50m |
| 2026-04-27 | LICHEN7 | - | Apr 27, 23:00 UTC | Apr 27, 23:05 UTC | 5m |
| 2026-04-27 | LICHEN7 | - | Apr 27, 22:50 UTC | Apr 27, 22:55 UTC | 5m |
| 2026-04-23 | R21200 | - | Apr 23, 21:05 UTC | Apr 23, 21:45 UTC | 40m |
| 2026-04-23 | R21200 | - | Apr 23, 19:10 UTC | Apr 23, 20:20 UTC | 1h 10m |
| 2026-04-23 | R21200 | FBK → FBK | Apr 23, 18:50 UTC | Apr 23, 18:55 UTC | 5m |
| 2026-04-23 | R21200 | FBK → FBK | Apr 23, 18:25 UTC | Apr 23, 18:35 UTC | 10m |
| 2026-04-23 | R21200 | FBK → FBK | Apr 23, 18:05 UTC | Apr 23, 18:10 UTC | 5m |
| 2026-04-23 | R21200 | - | Apr 23, 08:05 UTC | Apr 23, 09:20 UTC | 1h 15m |
| 2026-04-23 | R21200 | FBK → MLY | Apr 23, 06:50 UTC | Apr 23, 07:50 UTC | 1h 0m |
| 2026-04-22 | R21200 | FBK → FBK | Apr 22, 11:05 UTC | Apr 22, 11:10 UTC | 5m |
| 2026-04-22 | R21200 | - | Apr 22, 10:20 UTC | Apr 22, 11:00 UTC | 40m |
| 2026-04-22 | R21200 | - | Apr 22, 08:10 UTC | Apr 22, 09:45 UTC | 1h 35m |
| 2026-04-22 | R21200 | - | Apr 22, 07:00 UTC | Apr 22, 07:15 UTC | 15m |
| 2026-04-22 | R21200 | FBK → FBK | Apr 22, 06:30 UTC | Apr 22, 06:40 UTC | 10m |
| 2026-04-22 | R21200 | FBK → FBK | Apr 22, 06:15 UTC | Apr 22, 06:20 UTC | 5m |
| 2026-04-15 | R21200 | - | Apr 15, 00:55 UTC | Apr 15, 02:05 UTC | 1h 10m |
| 2026-04-15 | R21200 | - | Apr 15, 00:10 UTC | Apr 15, 00:50 UTC | 40m |
| 2026-04-14 | R21200 | - | Apr 14, 22:55 UTC | Apr 14, 23:40 UTC | 45m |
| 2026-04-14 | R21200 | - | Apr 14, 22:30 UTC | Apr 14, 22: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 21-21200 page for operator, model, and routing details .