sensors Mode-S transponder
AE216A
ICAO 24-bit transponder address
Currently assigned to 86-24539 · SIKORSKY UH-60 Black Hawk
- Hex
- AE216A
- Octal
- 53420552
- Decimal
- 11,411,818
- Tail
- 86-24539
- Type
- H60
- Flights observed
- 50
- Distinct callsigns
- 13
- Country
- -
- Last broadcast
- 9d ago
Last known position
Callsign history 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PIKES47 | - | 7 | 2026-06-20 |
| PIKES40 | - | 7 | 2026-05-26 |
| PIKES400 | - | 6 | 2026-05-05 |
| BELLS90 | - | 6 | 2026-06-24 |
| ARROW77 | - | 6 | 2026-07-01 |
| PIKES42 | - | 5 | 2026-07-02 |
| ARROW32 | - | 3 | 2026-07-08 |
| PIKES99 | - | 2 | 2026-05-08 |
| PIKES39 | - | 2 | 2026-05-08 |
| BELLS77 | - | 2 | 2026-05-20 |
| BELLS70 | - | 2 | 2026-07-07 |
| BELLS700 | - | 1 | 2026-06-18 |
| BELLS00 | - | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | ARROW32 | - | Jul 8, 03:45 UTC | Jul 8, 05:00 UTC | 1h 15m |
| 2026-07-08 | ARROW32 | BFK → CYS | Jul 8, 01:00 UTC | Jul 8, 02:00 UTC | 1h 0m |
| 2026-07-07 | BELLS70 | - | Jul 7, 21:20 UTC | Jul 7, 22:05 UTC | 45m |
| 2026-07-07 | BELLS70 | - | Jul 7, 21:00 UTC | Jul 7, 21:15 UTC | 15m |
| 2026-07-02 | PIKES42 | BFK → BFK | Jul 2, 03:25 UTC | Jul 2, 04:55 UTC | 1h 30m |
| 2026-07-02 | PIKES42 | BFK → BFK | Jul 2, 00:15 UTC | Jul 2, 02:00 UTC | 1h 45m |
| 2026-07-01 | ARROW77 | BFK → BFK | Jul 1, 18:45 UTC | Jul 1, 20:40 UTC | 1h 55m |
| 2026-06-24 | BELLS90 | - | Jun 24, 01:09 UTC | Jun 24, 01:24 UTC | 15m |
| 2026-06-20 | PIKES47 | - | Jun 20, 18:59 UTC | Jun 20, 19:44 UTC | 45m |
| 2026-06-20 | PIKES47 | - | Jun 20, 14:39 UTC | Jun 20, 16:05 UTC | 1h 25m |
| 2026-06-18 | BELLS700 | - | Jun 18, 20:50 UTC | Jun 18, 21:25 UTC | 35m |
| 2026-06-05 | ARROW77 | BFK → BFK | Jun 5, 03:50 UTC | Jun 5, 05:15 UTC | 1h 25m |
| 2026-06-05 | ARROW77 | BFK → BFK | Jun 5, 01:35 UTC | Jun 5, 03:35 UTC | 2h 0m |
| 2026-06-04 | BELLS00 | BFK → BFK | Jun 4, 01:35 UTC | Jun 4, 03:20 UTC | 1h 45m |
| 2026-06-03 | ARROW77 | - | Jun 3, 05:00 UTC | Jun 3, 05:40 UTC | 40m |
| 2026-06-03 | ARROW77 | - | Jun 3, 03:50 UTC | Jun 3, 04:05 UTC | 15m |
| 2026-06-03 | ARROW77 | - | Jun 3, 01:10 UTC | Jun 3, 02:30 UTC | 1h 20m |
| 2026-05-26 | PIKES40 | - | May 26, 20:29 UTC | May 26, 20:50 UTC | 20m |
| 2026-05-26 | PIKES40 | - | May 26, 20:09 UTC | May 26, 20:20 UTC | 10m |
| 2026-05-26 | PIKES40 | - | May 26, 19:15 UTC | May 26, 19:55 UTC | 40m |
| 2026-05-26 | PIKES40 | BFK → BFK | May 26, 18:55 UTC | May 26, 19:10 UTC | 15m |
| 2026-05-23 | PIKES40 | BFK → BFK | May 23, 16:00 UTC | May 23, 16:10 UTC | 10m |
| 2026-05-23 | PIKES40 | BFK → BFK | May 23, 15:35 UTC | May 23, 15:55 UTC | 20m |
| 2026-05-21 | PIKES40 | - | May 21, 00:05 UTC | May 21, 01:10 UTC | 1h 5m |
| 2026-05-20 | BELLS77 | - | May 20, 22:10 UTC | May 20, 22:35 UTC | 25m |
| 2026-05-20 | BELLS77 | - | May 20, 16:15 UTC | May 20, 16:40 UTC | 25m |
| 2026-05-19 | PIKES47 | BFK → BFK | May 19, 20:10 UTC | May 19, 21:50 UTC | 1h 40m |
| 2026-05-08 | PIKES39 | - | May 8, 16:40 UTC | May 8, 17:20 UTC | 40m |
| 2026-05-08 | PIKES39 | - | May 8, 14:15 UTC | May 8, 14:35 UTC | 20m |
| 2026-05-08 | PIKES99 | - | May 8, 03:09 UTC | May 8, 04:34 UTC | 1h 25m |
| 2026-05-08 | PIKES99 | BFK → BFK | May 8, 00:54 UTC | May 8, 02:04 UTC | 1h 10m |
| 2026-05-07 | BELLS90 | - | May 7, 02:35 UTC | May 7, 03:25 UTC | 50m |
| 2026-05-06 | BELLS90 | BFK → BFK | May 6, 23:45 UTC | May 7, 01:40 UTC | 1h 55m |
| 2026-05-05 | PIKES400 | BFK → BFK | May 5, 03:10 UTC | May 5, 04:15 UTC | 1h 5m |
| 2026-05-05 | PIKES400 | - | May 5, 01:40 UTC | May 5, 02:01 UTC | 20m |
| 2026-05-05 | PIKES400 | - | May 5, 00:45 UTC | May 5, 01:30 UTC | 45m |
| 2026-05-05 | PIKES400 | BFK → BFK | May 5, 00:30 UTC | May 5, 00:40 UTC | 10m |
| 2026-05-05 | PIKES400 | BFK → BFK | May 5, 00:05 UTC | May 5, 00:25 UTC | 20m |
| 2026-05-04 | PIKES400 | BFK → BFK | May 4, 23:45 UTC | May 5, 00:00 UTC | 15m |
| 2026-05-01 | PIKES47 | - | May 1, 20:55 UTC | May 1, 21:35 UTC | 40m |
| 2026-05-01 | PIKES47 | - | May 1, 16:40 UTC | May 1, 18:25 UTC | 1h 45m |
| 2026-04-30 | ARROW32 | BFK → BFK | Apr 30, 18:05 UTC | Apr 30, 19:00 UTC | 55m |
| 2026-04-17 | PIKES47 | - | Apr 17, 01:20 UTC | Apr 17, 02:20 UTC | 1h 0m |
| 2026-04-17 | PIKES47 | - | Apr 17, 00:20 UTC | Apr 17, 01:15 UTC | 55m |
| 2026-04-16 | PIKES42 | - | Apr 16, 19:15 UTC | Apr 16, 20:25 UTC | 1h 10m |
| 2026-04-16 | BELLS90 | - | Apr 16, 03:19 UTC | Apr 16, 04:20 UTC | 1h 0m |
| 2026-04-16 | BELLS90 | - | Apr 16, 01:10 UTC | Apr 16, 02:09 UTC | 1h 0m |
| 2026-04-16 | BELLS90 | - | Apr 16, 00:15 UTC | Apr 16, 01:05 UTC | 50m |
| 2026-04-15 | PIKES42 | - | Apr 15, 21:05 UTC | Apr 15, 21:30 UTC | 25m |
| 2026-04-15 | PIKES42 | - | Apr 15, 19:40 UTC | Apr 15, 21:00 UTC | 1h 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 86-24539 page for operator, model, and routing details .