sensors Mode-S transponder
AE0DD4
ICAO 24-bit transponder address
Currently assigned to 84-23960 · SIKORSKY UH-60 Black Hawk
- Hex
- AE0DD4
- Octal
- 53406724
- Decimal
- 11,406,804
- Tail
- 84-23960
- Type
- H60
- Flights observed
- 28
- Distinct callsigns
- 8
- Country
- -
- Last broadcast
- Jun 11, 03:35 UTC
Last known position
Callsign history 8 distinct
Recent flights last 28
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | ARROW32 | BFK → BFK | Jun 11, 02:10 UTC | Jun 11, 03:35 UTC | 1h 25m |
| 2026-06-10 | PIKES42 | BFK → BFK | Jun 10, 21:40 UTC | Jun 10, 23:45 UTC | 2h 5m |
| 2026-06-04 | BELLS76 | - | Jun 4, 21:55 UTC | Jun 4, 22:40 UTC | 45m |
| 2026-06-04 | BELLS76 | - | Jun 4, 18:30 UTC | Jun 4, 19:50 UTC | 1h 20m |
| 2026-06-04 | BELLS76 | BFK → CNE | Jun 4, 14:40 UTC | Jun 4, 15:25 UTC | 45m |
| 2026-06-03 | PIKES40 | BFK → BFK | Jun 3, 23:40 UTC | Jun 4, 00:45 UTC | 1h 5m |
| 2026-06-03 | PIKES40 | BFK → BFK | Jun 3, 23:15 UTC | Jun 3, 23:25 UTC | 10m |
| 2026-06-03 | PIKES40 | BFK → BFK | Jun 3, 21:25 UTC | Jun 3, 21:35 UTC | 10m |
| 2026-06-03 | PIKES40 | BFK → BFK | Jun 3, 20:50 UTC | Jun 3, 21:00 UTC | 10m |
| 2026-06-03 | PIKES40 | BFK → BFK | Jun 3, 20:30 UTC | Jun 3, 20:45 UTC | 15m |
| 2026-06-03 | BELLS76 | - | Jun 3, 18:00 UTC | Jun 3, 18:45 UTC | 45m |
| 2026-05-27 | ARROW77 | - | May 27, 03:34 UTC | May 27, 04:59 UTC | 1h 25m |
| 2026-05-27 | ARROW77 | - | May 27, 01:14 UTC | May 27, 01:24 UTC | 10m |
| 2026-05-26 | BELLS76 | BFK → BFK | May 26, 19:45 UTC | May 26, 20:24 UTC | 40m |
| 2026-05-20 | PIKES32 | - | May 20, 21:05 UTC | May 20, 21:15 UTC | 10m |
| 2026-05-20 | PIKES32 | BFK → BFK | May 20, 20:00 UTC | May 20, 20:20 UTC | 20m |
| 2026-05-12 | BELLS70 | - | May 12, 22:10 UTC | May 12, 22:40 UTC | 30m |
| 2026-05-12 | BELLS70 | - | May 12, 21:25 UTC | May 12, 22:01 UTC | 35m |
| 2026-05-12 | BELLS70 | - | May 12, 14:10 UTC | May 12, 14:45 UTC | 35m |
| 2026-05-12 | BELLS70 | BFK → COS | May 12, 13:15 UTC | May 12, 13:51 UTC | 35m |
| 2026-05-08 | PIKES32 | BFK → BFK | May 8, 21:05 UTC | May 8, 21:50 UTC | 45m |
| 2026-05-07 | ARROW32 | - | May 7, 17:55 UTC | May 7, 18:05 UTC | 10m |
| 2026-04-22 | BELLS70 | - | Apr 22, 14:30 UTC | Apr 22, 14:50 UTC | 20m |
| 2026-04-17 | PIKES40 | BFK → BFK | Apr 17, 15:40 UTC | Apr 17, 15:50 UTC | 10m |
| 2026-04-17 | PIKES40 | BFK → BFK | Apr 17, 15:25 UTC | Apr 17, 15:35 UTC | 10m |
| 2026-04-17 | PIKES40 | - | Apr 17, 14:55 UTC | Apr 17, 15:15 UTC | 20m |
| 2026-04-16 | PIKES47 | - | Apr 16, 20:30 UTC | Apr 16, 20:50 UTC | 20m |
| 2026-04-16 | PIKES47 | - | Apr 16, 17:15 UTC | Apr 16, 17:35 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 84-23960 page for operator, model, and routing details .