sensors Mode-S transponder
AE4FDD
ICAO 24-bit transponder address
Currently assigned to 168141 · SIKORSKY UH-60 Black Hawk
- Hex
- AE4FDD
- Octal
- 53447735
- Decimal
- 11,423,709
- Tail
- 168141
- Type
- H60
- Flights observed
- 30
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- 4d ago
Current position
Callsign history 2 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VVHR514 | - | Jul 17, 01:59 UTC | Jul 17, 02:34 UTC | 35m |
| 2026-07-16 | VVHR514 | - | Jul 16, 22:35 UTC | Jul 16, 23:44 UTC | 1h 10m |
| 2026-07-16 | VVHR514 | - | Jul 16, 20:55 UTC | Jul 16, 21:25 UTC | 30m |
| 2026-07-16 | VVHR514 | - | Jul 16, 17:10 UTC | Jul 16, 17:49 UTC | 40m |
| 2026-07-14 | VVHR514 | - | Jul 14, 22:55 UTC | Jul 14, 23:30 UTC | 35m |
| 2026-07-14 | VVHR514 | - | Jul 14, 21:00 UTC | Jul 14, 21:45 UTC | 45m |
| 2026-07-14 | VVHR514 | - | Jul 14, 18:30 UTC | Jul 14, 19:55 UTC | 1h 25m |
| 2026-07-09 | VVHR514 | - | Jul 9, 20:50 UTC | Jul 9, 22:55 UTC | 2h 5m |
| 2026-07-08 | VVHR514 | - | Jul 8, 00:10 UTC | Jul 8, 01:15 UTC | 1h 5m |
| 2026-07-07 | VVHR514 | - | Jul 7, 22:25 UTC | Jul 7, 22:55 UTC | 30m |
| 2026-07-07 | VVHR514 | - | Jul 7, 20:40 UTC | Jul 7, 21:05 UTC | 25m |
| 2026-07-07 | VVHR514 | - | Jul 7, 18:10 UTC | Jul 7, 18:30 UTC | 20m |
| 2026-06-05 | VVHR514 | - | Jun 5, 17:05 UTC | Jun 5, 17:15 UTC | 10m |
| 2026-06-03 | VVHR513 | - | Jun 3, 22:20 UTC | Jun 3, 22:40 UTC | 20m |
| 2026-05-27 | VVHR514 | - | May 27, 22:40 UTC | May 27, 22:50 UTC | 10m |
| 2026-05-27 | VVHR514 | - | May 27, 17:15 UTC | May 27, 18:30 UTC | 1h 15m |
| 2026-05-20 | VVHR514 | - | May 20, 22:20 UTC | May 20, 22:30 UTC | 10m |
| 2026-05-20 | VVHR514 | - | May 20, 15:55 UTC | May 20, 17:00 UTC | 1h 5m |
| 2026-05-18 | VVHR514 | - | May 18, 22:25 UTC | May 18, 22:50 UTC | 25m |
| 2026-05-18 | VVHR514 | - | May 18, 18:25 UTC | May 18, 18:45 UTC | 19m |
| 2026-05-07 | VVHR514 | - | May 7, 21:50 UTC | May 7, 22:40 UTC | 50m |
| 2026-05-07 | VVHR514 | - | May 7, 16:00 UTC | May 7, 16:40 UTC | 40m |
| 2026-05-06 | VVHR514 | - | May 6, 23:45 UTC | May 7, 01:10 UTC | 1h 25m |
| 2026-05-06 | VVHR514 | - | May 6, 16:00 UTC | May 6, 16:25 UTC | 25m |
| 2026-04-30 | VVHR514 | - | Apr 30, 20:50 UTC | Apr 30, 21:05 UTC | 15m |
| 2026-04-30 | VVHR514 | - | Apr 30, 15:45 UTC | Apr 30, 16:10 UTC | 25m |
| 2026-04-27 | VVHR514 | - | Apr 27, 19:10 UTC | Apr 27, 19:25 UTC | 15m |
| 2026-04-24 | VVHR514 | - | Apr 24, 19:10 UTC | Apr 24, 19:35 UTC | 25m |
| 2026-04-17 | VVHR514 | - | Apr 17, 00:25 UTC | Apr 17, 01:00 UTC | 35m |
| 2026-04-16 | - | NRB → NRB | Apr 16, 22:24 UTC | Apr 16, 22:34 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 168141 page for operator, model, and routing details .