sensors Mode-S transponder
AE5F15
ICAO 24-bit transponder address
Currently assigned to 17-5870 · Lockheed Martin HC-130J Combat King II
- Hex
- AE5F15
- Octal
- 53457425
- Decimal
- 11,427,605
- Tail
- 17-5870
- Type
- C30J
- Flights observed
- 46
- Distinct callsigns
- 4
- Country
- -
- Last broadcast
- 5d ago
Last known position
Callsign history 4 distinct
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | KING70 | - | Jul 8, 15:15 UTC | Jul 8, 18:30 UTC | 3h 15m |
| 2026-07-05 | KING70 | - | Jul 5, 13:35 UTC | Jul 5, 15:00 UTC | 1h 25m |
| 2026-07-04 | RODEO31 | - | Jul 4, 13:05 UTC | Jul 4, 15:30 UTC | 2h 25m |
| 2026-07-04 | RODEO32 | - | Jul 4, 11:20 UTC | Jul 4, 11:55 UTC | 35m |
| 2026-07-03 | KING70 | - | Jul 3, 12:50 UTC | Jul 3, 16:55 UTC | 4h 5m |
| 2026-07-02 | 175870 | - | Jul 2, 16:35 UTC | Jul 2, 17:35 UTC | 1h 0m |
| 2026-07-02 | KING70 | - | Jul 2, 14:15 UTC | Jul 2, 15:30 UTC | 1h 15m |
| 2026-07-02 | KING70 | - | Jul 2, 01:30 UTC | Jul 2, 03:05 UTC | 1h 35m |
| 2026-07-01 | KING70 | - | Jul 1, 17:55 UTC | Jul 1, 18:25 UTC | 30m |
| 2026-07-01 | KING70 | - | Jul 1, 15:00 UTC | Jul 1, 15:50 UTC | 50m |
| 2026-07-01 | KING70 | - | Jul 1, 01:25 UTC | Jul 1, 02:45 UTC | 1h 20m |
| 2026-06-30 | KING70 | - | Jun 30, 23:20 UTC | Jul 1, 00:50 UTC | 1h 30m |
| 2026-06-30 | KING70 | - | Jun 30, 17:25 UTC | Jun 30, 18:35 UTC | 1h 10m |
| 2026-06-30 | KING70 | - | Jun 30, 15:15 UTC | Jun 30, 16:00 UTC | 45m |
| 2026-06-26 | KING70 | - | Jun 26, 15:05 UTC | Jun 26, 17:59 UTC | 2h 55m |
| 2026-06-17 | KING70 | - | Jun 17, 23:05 UTC | Jun 18, 01:15 UTC | 2h 10m |
| 2026-06-16 | KING70 | - | Jun 16, 15:24 UTC | Jun 16, 18:39 UTC | 3h 15m |
| 2026-06-12 | KING70 | - | Jun 12, 14:01 UTC | Jun 12, 16:30 UTC | 2h 30m |
| 2026-05-28 | KING70 | - | May 28, 23:00 UTC | May 29, 02:40 UTC | 3h 40m |
| 2026-05-28 | KING70 | - | May 28, 16:30 UTC | May 28, 18:25 UTC | 1h 55m |
| 2026-05-28 | KING70 | - | May 28, 15:05 UTC | May 28, 15:15 UTC | 10m |
| 2026-05-27 | KING70 | - | May 27, 23:00 UTC | May 28, 02:45 UTC | 3h 45m |
| 2026-05-27 | KING70 | - | May 27, 14:55 UTC | May 27, 18:30 UTC | 3h 35m |
| 2026-05-22 | KING70 | - | May 22, 16:05 UTC | May 22, 18:10 UTC | 2h 5m |
| 2026-05-15 | KING70 | - | May 15, 18:45 UTC | May 15, 20:15 UTC | 1h 30m |
| 2026-05-15 | KING70 | - | May 15, 14:45 UTC | May 15, 15:55 UTC | 1h 9m |
| 2026-05-13 | KING70 | - | May 13, 20:40 UTC | May 13, 22:50 UTC | 2h 10m |
| 2026-05-13 | KING70 | - | May 13, 18:35 UTC | May 13, 19:45 UTC | 1h 10m |
| 2026-05-12 | KING70 | - | May 12, 22:25 UTC | May 12, 23:15 UTC | 50m |
| 2026-05-12 | KING70 | - | May 12, 18:55 UTC | May 12, 20:35 UTC | 1h 40m |
| 2026-05-12 | KING70 | - | May 12, 16:40 UTC | May 12, 18:20 UTC | 1h 40m |
| 2026-05-08 | KING70 | - | May 8, 17:45 UTC | May 8, 18:20 UTC | 35m |
| 2026-05-07 | KING70 | - | May 7, 19:00 UTC | May 7, 20:35 UTC | 1h 35m |
| 2026-05-06 | KING70 | - | May 6, 15:10 UTC | May 6, 17:30 UTC | 2h 20m |
| 2026-05-05 | KING70 | - | May 5, 23:05 UTC | May 5, 23:45 UTC | 40m |
| 2026-05-05 | KING70 | - | May 5, 15:10 UTC | May 5, 18:30 UTC | 3h 20m |
| 2026-04-28 | KING70 | - | Apr 28, 20:20 UTC | Apr 28, 22:35 UTC | 2h 15m |
| 2026-04-28 | KING70 | - | Apr 28, 17:05 UTC | Apr 28, 19:35 UTC | 2h 30m |
| 2026-04-23 | KING70 | - | Apr 23, 22:30 UTC | Apr 24, 02:00 UTC | 3h 30m |
| 2026-04-23 | KING70 | - | Apr 23, 15:20 UTC | Apr 23, 18:35 UTC | 3h 14m |
| 2026-04-23 | KING70 | - | Apr 23, 01:40 UTC | Apr 23, 02:25 UTC | 45m |
| 2026-04-22 | KING70 | - | Apr 22, 23:00 UTC | Apr 23, 01:00 UTC | 2h 0m |
| 2026-04-22 | KING70 | - | Apr 22, 00:10 UTC | Apr 22, 02:30 UTC | 2h 20m |
| 2026-04-21 | KING70 | - | Apr 21, 18:25 UTC | Apr 21, 21:10 UTC | 2h 45m |
| 2026-04-21 | KING70 | - | Apr 21, 17:15 UTC | Apr 21, 17:50 UTC | 35m |
| 2026-04-21 | KING70 | - | Apr 21, 14:20 UTC | Apr 21, 16:45 UTC | 2h 25m |
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 17-5870 page for operator, model, and routing details .