sensors Mode-S transponder
AE08E6
ICAO 24-bit transponder address
Currently assigned to 73-1217 · BEECH 200 Super King Air
- Hex
- AE08E6
- Octal
- 53404346
- Decimal
- 11,405,542
- Tail
- 73-1217
- Type
- BE20
- Flights observed
- 40
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- Jul 24, 03:00 UTC
Last known position
Callsign history 3 distinct
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | TITUS06 | DNA → OKO | Jul 23, 23:30 UTC | Jul 24, 03:00 UTC | 3h 30m |
| 2026-07-23 | TITUS06 | - | Jul 23, 03:15 UTC | Jul 23, 04:05 UTC | 50m |
| 2026-07-17 | VIPER17 | - | Jul 17, 02:20 UTC | Jul 17, 02:59 UTC | 40m |
| 2026-07-16 | VIPER17 | - | Jul 16, 23:55 UTC | Jul 17, 00:35 UTC | 40m |
| 2026-07-14 | VIPER17 | - | Jul 14, 02:05 UTC | Jul 14, 02:50 UTC | 45m |
| 2026-07-13 | VIPER17 | - | Jul 13, 23:40 UTC | Jul 14, 00:15 UTC | 35m |
| 2026-07-07 | VIPER17 | - | Jul 7, 09:15 UTC | Jul 7, 10:15 UTC | 1h 0m |
| 2026-07-06 | VIPER17 | - | Jul 6, 23:50 UTC | Jul 7, 00:40 UTC | 50m |
| 2026-07-01 | VIPER17 | - | Jul 1, 09:15 UTC | Jul 1, 09:55 UTC | 40m |
| 2026-06-30 | VIPER17 | - | Jun 30, 23:15 UTC | Jul 1, 00:05 UTC | 50m |
| 2026-06-30 | VIPER17 | - | Jun 30, 08:25 UTC | Jun 30, 08:45 UTC | 20m |
| 2026-06-29 | VIPER17 | - | Jun 29, 23:39 UTC | Jun 30, 00:00 UTC | 20m |
| 2026-06-22 | VIPER17 | - | Jun 22, 07:49 UTC | Jun 22, 08:25 UTC | 35m |
| 2026-06-21 | VIPER17 | - | Jun 21, 22:34 UTC | Jun 21, 23:05 UTC | 30m |
| 2026-06-18 | VIPER17 | - | Jun 18, 07:45 UTC | Jun 18, 08:35 UTC | 50m |
| 2026-06-18 | VIPER17 | - | Jun 18, 00:00 UTC | Jun 18, 00:55 UTC | 55m |
| 2026-06-12 | TITUS71 | - | Jun 12, 05:55 UTC | Jun 12, 06:30 UTC | 35m |
| 2026-06-10 | TITUS71 | - | Jun 10, 02:35 UTC | Jun 10, 03:15 UTC | 40m |
| 2026-06-01 | VIPER17 | - | Jun 1, 06:00 UTC | Jun 1, 07:10 UTC | 1h 10m |
| 2026-06-01 | VIPER17 | - | Jun 1, 00:05 UTC | Jun 1, 00:50 UTC | 45m |
| 2026-05-29 | VIPER17 | - | May 29, 03:40 UTC | May 29, 04:05 UTC | 25m |
| 2026-05-28 | VIPER17 | - | May 28, 23:50 UTC | May 29, 00:00 UTC | 10m |
| 2026-05-26 | VIPER17 | - | May 26, 05:20 UTC | May 26, 05:49 UTC | 30m |
| 2026-05-26 | VIPER17 | - | May 26, 02:00 UTC | May 26, 02:39 UTC | 40m |
| 2026-05-25 | VIPER17 | - | May 25, 23:45 UTC | May 26, 00:24 UTC | 40m |
| 2026-05-20 | VIPER17 | - | May 20, 03:10 UTC | May 20, 04:00 UTC | 50m |
| 2026-05-19 | VIPER17 | - | May 19, 23:20 UTC | May 20, 00:15 UTC | 55m |
| 2026-05-18 | VIPER17 | - | May 18, 03:55 UTC | May 18, 04:45 UTC | 50m |
| 2026-05-17 | VIPER17 | - | May 17, 23:20 UTC | May 18, 00:05 UTC | 45m |
| 2026-05-06 | VIPER17 | - | May 6, 05:00 UTC | May 6, 06:05 UTC | 1h 4m |
| 2026-05-05 | VIPER17 | - | May 5, 22:40 UTC | May 5, 23:20 UTC | 40m |
| 2026-05-04 | VIPER17 | - | May 4, 04:24 UTC | May 4, 05:10 UTC | 45m |
| 2026-05-03 | VIPER17 | - | May 3, 22:00 UTC | May 3, 22:39 UTC | 40m |
| 2026-04-30 | VIPER17 | - | Apr 30, 05:20 UTC | Apr 30, 06:20 UTC | 1h 0m |
| 2026-04-30 | VIPER17 | - | Apr 30, 00:55 UTC | Apr 30, 01:50 UTC | 55m |
| 2026-04-22 | VIPER17 | - | Apr 22, 08:30 UTC | Apr 22, 09:20 UTC | 50m |
| 2026-04-21 | VIPER17 | - | Apr 21, 23:40 UTC | Apr 22, 00:25 UTC | 45m |
| 2026-04-17 | VIPER17 | - | Apr 17, 05:55 UTC | Apr 17, 06:40 UTC | 45m |
| 2026-04-17 | VIPER17 | - | Apr 17, 01:20 UTC | Apr 17, 01:40 UTC | 20m |
| 2026-04-17 | VIPER17 | - | Apr 17, 00:50 UTC | Apr 17, 01:15 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 73-1217 page for operator, model, and routing details .