sensors Mode-S transponder
AE5F09
ICAO 24-bit transponder address
Currently assigned to 16-5851 · Lockheed Martin C-130J-30 Hercules
- Hex
- AE5F09
- Octal
- 53457411
- Decimal
- 11,427,593
- Tail
- 16-5851
- Type
- C30J
- Flights observed
- 62
- Distinct callsigns
- 16
- Country
- -
- Last broadcast
- 2d ago
Last known position
Callsign history 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ROPER91 | - | 15 | 2026-06-15 |
| ROPER61 | - | 8 | 2026-05-28 |
| ROPER60 | - | 6 | 2026-07-17 |
| RCH627 | - | 4 | 2026-07-01 |
| HKY747 | - | 4 | 2026-06-26 |
| HKY720 | - | 4 | 2026-06-05 |
| ROPER94 | - | 3 | 2026-04-29 |
| RCH624 | Air Mobility Command | 3 | 2026-06-01 |
| HKY603 | - | 3 | 2026-06-23 |
| HKY743 | - | 2 | 2026-06-18 |
| HKY741 | - | 2 | 2026-06-19 |
| HKY733 | - | 2 | 2026-06-09 |
| HKY604 | - | 2 | 2026-06-16 |
| 165851 | - | 2 | 2026-05-27 |
| ROPER63 | - | 1 | 2026-05-21 |
| ROPER62 | - | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | ROPER60 | - | Jul 17, 00:40 UTC | Jul 17, 02:59 UTC | 2h 20m |
| 2026-07-14 | ROPER60 | - | Jul 14, 16:00 UTC | Jul 14, 17:50 UTC | 1h 50m |
| 2026-07-01 | RCH627 | - | Jul 1, 18:05 UTC | Jul 1, 22:55 UTC | 4h 50m |
| 2026-07-01 | RCH627 | - | Jul 1, 15:15 UTC | Jul 1, 17:10 UTC | 1h 55m |
| 2026-06-30 | RCH627 | - | Jun 30, 12:30 UTC | Jun 30, 14:30 UTC | 2h 0m |
| 2026-06-30 | RCH627 | - | Jun 30, 09:20 UTC | Jun 30, 10:40 UTC | 1h 20m |
| 2026-06-26 | HKY747 | - | Jun 26, 12:14 UTC | Jun 26, 15:10 UTC | 2h 55m |
| 2026-06-26 | HKY747 | - | Jun 26, 07:45 UTC | Jun 26, 10:44 UTC | 3h 0m |
| 2026-06-25 | HKY747 | - | Jun 25, 13:05 UTC | Jun 25, 16:05 UTC | 3h 0m |
| 2026-06-25 | HKY747 | - | Jun 25, 08:14 UTC | Jun 25, 11:10 UTC | 2h 55m |
| 2026-06-23 | HKY603 | - | Jun 23, 17:15 UTC | Jun 23, 18:29 UTC | 1h 15m |
| 2026-06-23 | HKY603 | TMP → LKZ | Jun 23, 13:00 UTC | Jun 23, 16:20 UTC | 3h 20m |
| 2026-06-23 | HKY603 | - | Jun 23, 06:59 UTC | Jun 23, 09:54 UTC | 2h 55m |
| 2026-06-19 | HKY741 | - | Jun 19, 16:09 UTC | Jun 19, 19:59 UTC | 3h 50m |
| 2026-06-19 | HKY741 | - | Jun 19, 07:14 UTC | Jun 19, 10:54 UTC | 3h 40m |
| 2026-06-18 | HKY743 | - | Jun 18, 11:35 UTC | Jun 18, 14:35 UTC | 3h 0m |
| 2026-06-18 | HKY743 | - | Jun 18, 07:05 UTC | Jun 18, 10:00 UTC | 2h 55m |
| 2026-06-16 | HKY604 | RZE → RMS | Jun 16, 12:35 UTC | Jun 16, 14:39 UTC | 2h 5m |
| 2026-06-16 | HKY604 | RMS → RZE | Jun 16, 09:25 UTC | Jun 16, 11:25 UTC | 2h 0m |
| 2026-06-15 | ROPER91 | - | Jun 15, 10:20 UTC | Jun 15, 11:19 UTC | 1h 0m |
| 2026-06-09 | ROPER91 | - | Jun 9, 16:45 UTC | Jun 9, 17:25 UTC | 40m |
| 2026-06-09 | HKY733 | - | Jun 9, 08:25 UTC | Jun 9, 12:10 UTC | 3h 45m |
| 2026-06-08 | HKY733 | - | Jun 8, 06:10 UTC | Jun 8, 08:35 UTC | 2h 25m |
| 2026-06-05 | HKY720 | - | Jun 5, 06:15 UTC | Jun 5, 10:15 UTC | 4h 0m |
| 2026-06-04 | HKY720 | - | Jun 4, 05:20 UTC | Jun 4, 06:05 UTC | 45m |
| 2026-06-04 | HKY720 | - | Jun 4, 01:45 UTC | Jun 4, 03:30 UTC | 1h 45m |
| 2026-06-03 | HKY720 | - | Jun 3, 20:55 UTC | Jun 3, 23:20 UTC | 2h 25m |
| 2026-06-01 | RCH624 | - | Jun 1, 06:30 UTC | Jun 1, 09:05 UTC | 2h 35m |
| 2026-05-31 | RCH624 | - | May 31, 20:50 UTC | May 31, 22:30 UTC | 1h 40m |
| 2026-05-30 | RCH624 | - | May 30, 15:15 UTC | May 30, 19:35 UTC | 4h 20m |
| 2026-05-28 | ROPER61 | - | May 28, 00:55 UTC | May 28, 02:10 UTC | 1h 15m |
| 2026-05-27 | ROPER61 | - | May 27, 23:20 UTC | May 27, 23:40 UTC | 20m |
| 2026-05-27 | ROPER61 | - | May 27, 19:25 UTC | May 27, 19:35 UTC | 10m |
| 2026-05-27 | ROPER61 | - | May 27, 18:40 UTC | May 27, 18:55 UTC | 15m |
| 2026-05-27 | ROPER61 | - | May 27, 16:15 UTC | May 27, 17:05 UTC | 50m |
| 2026-05-27 | 165851 | - | May 27, 01:09 UTC | May 27, 01:39 UTC | 30m |
| 2026-05-27 | 165851 | - | May 27, 00:14 UTC | May 27, 00:30 UTC | 15m |
| 2026-05-21 | ROPER63 | - | May 21, 18:20 UTC | May 21, 18:30 UTC | 10m |
| 2026-05-14 | ROPER60 | - | May 14, 22:20 UTC | May 15, 00:15 UTC | 1h 55m |
| 2026-05-08 | ROPER62 | - | May 8, 02:24 UTC | May 8, 02:44 UTC | 20m |
| 2026-05-06 | ROPER60 | FWH → FWH | May 6, 00:40 UTC | May 6, 02:45 UTC | 2h 5m |
| 2026-05-01 | ROPER61 | - | May 1, 02:45 UTC | May 1, 03:05 UTC | 20m |
| 2026-05-01 | ROPER60 | - | May 1, 00:35 UTC | May 1, 01:35 UTC | 1h 0m |
| 2026-04-30 | ROPER61 | - | Apr 30, 02:15 UTC | Apr 30, 02:40 UTC | 25m |
| 2026-04-30 | ROPER61 | - | Apr 30, 00:15 UTC | Apr 30, 00:40 UTC | 25m |
| 2026-04-29 | ROPER94 | - | Apr 29, 20:25 UTC | Apr 29, 21:05 UTC | 40m |
| 2026-04-29 | ROPER94 | OKC → OKC | Apr 29, 17:45 UTC | Apr 29, 20:00 UTC | 2h 15m |
| 2026-04-29 | ROPER94 | - | Apr 29, 15:25 UTC | Apr 29, 16:00 UTC | 35m |
| 2026-04-21 | ROPER60 | - | Apr 21, 16:15 UTC | Apr 21, 18:10 UTC | 1h 55m |
| 2026-04-15 | ROPER91 | - | Apr 15, 23:10 UTC | Apr 15, 23:35 UTC | 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 16-5851 page for operator, model, and routing details .