sensors Mode-S transponder
AE54C3
ICAO 24-bit transponder address
Currently assigned to 14-00066 · Raytheon T-6D Texan II
- Hex
- AE54C3
- Octal
- 53452303
- Decimal
- 11,424,963
- Tail
- 14-00066
- Type
- TEX2
- Flights observed
- 52
- Distinct callsigns
- 12
- Country
- -
- Last broadcast
- Jul 22, 19:55 UTC
Last known position
Callsign history 12 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | EVAL53 | - | Jul 22, 18:25 UTC | Jul 22, 19:55 UTC | 1h 30m |
| 2026-07-22 | EVAL53 | - | Jul 22, 14:35 UTC | Jul 22, 16:05 UTC | 1h 30m |
| 2026-07-21 | EVAL99 | - | Jul 21, 14:35 UTC | Jul 21, 16:05 UTC | 1h 30m |
| 2026-07-21 | EVAL99 | - | Jul 21, 00:35 UTC | Jul 21, 01:45 UTC | 1h 10m |
| 2026-07-20 | EVAL99 | - | Jul 20, 22:45 UTC | Jul 20, 23:35 UTC | 50m |
| 2026-07-20 | EVAL53 | - | Jul 20, 16:50 UTC | Jul 20, 17:00 UTC | 10m |
| 2026-07-20 | EVAL53 | - | Jul 20, 15:15 UTC | Jul 20, 16:15 UTC | 1h 0m |
| 2026-07-18 | EVAL60 | - | Jul 18, 00:25 UTC | Jul 18, 01:20 UTC | 55m |
| 2026-07-17 | EVAL60 | - | Jul 17, 21:50 UTC | Jul 17, 22:40 UTC | 50m |
| 2026-07-17 | EVAL60 | - | Jul 17, 19:35 UTC | Jul 17, 20:29 UTC | 55m |
| 2026-07-17 | EVAL60 | - | Jul 17, 15:29 UTC | Jul 17, 16:19 UTC | 50m |
| 2026-07-17 | EVAL60 | - | Jul 17, 12:50 UTC | Jul 17, 14:04 UTC | 1h 15m |
| 2026-07-16 | EVAL53 | - | Jul 16, 19:45 UTC | Jul 16, 20:49 UTC | 1h 5m |
| 2026-07-15 | EVAL53 | - | Jul 15, 16:35 UTC | Jul 15, 17:05 UTC | 30m |
| 2026-07-14 | EVAL63 | HUA → HUA | Jul 14, 17:35 UTC | Jul 14, 17:45 UTC | 10m |
| 2026-07-13 | EVAL99 | - | Jul 13, 18:25 UTC | Jul 13, 19:55 UTC | 1h 30m |
| 2026-07-13 | EVAL63 | - | Jul 13, 13:45 UTC | Jul 13, 15:10 UTC | 1h 25m |
| 2026-07-09 | EVAL63 | - | Jul 9, 17:20 UTC | Jul 9, 18:30 UTC | 1h 10m |
| 2026-07-09 | EVAL63 | - | Jul 9, 12:40 UTC | Jul 9, 13:40 UTC | 1h 0m |
| 2026-07-01 | EVAL53 | HUA → HUA | Jul 1, 18:25 UTC | Jul 1, 19:55 UTC | 1h 30m |
| 2026-06-30 | EVAL53 | HUA → HUA | Jun 30, 21:00 UTC | Jun 30, 22:30 UTC | 1h 30m |
| 2026-06-30 | EVAL53 | - | Jun 30, 19:35 UTC | Jun 30, 19:50 UTC | 15m |
| 2026-06-30 | EVAL53 | - | Jun 30, 18:10 UTC | Jun 30, 19:00 UTC | 50m |
| 2026-06-26 | EVAL75 | - | Jun 26, 16:20 UTC | Jun 26, 17:44 UTC | 1h 25m |
| 2026-06-23 | EVAL59 | - | Jun 23, 18:10 UTC | Jun 23, 19:29 UTC | 1h 20m |
| 2026-05-19 | EVAL44 | - | May 19, 17:50 UTC | May 19, 18:50 UTC | 1h 0m |
| 2026-05-19 | EVAL44 | HUA → HUA | May 19, 14:55 UTC | May 19, 16:20 UTC | 1h 25m |
| 2026-05-15 | EVAL44 | - | May 15, 18:35 UTC | May 15, 20:20 UTC | 1h 45m |
| 2026-05-15 | EVAL43 | - | May 15, 15:45 UTC | May 15, 17:35 UTC | 1h 50m |
| 2026-05-11 | EVAL53 | - | May 11, 18:35 UTC | May 11, 18:45 UTC | 10m |
| 2026-05-11 | EVAL53 | - | May 11, 17:05 UTC | May 11, 17:55 UTC | 50m |
| 2026-05-08 | EVAL40 | HUA → HUA | May 8, 19:30 UTC | May 8, 21:05 UTC | 1h 35m |
| 2026-05-07 | EVAL53 | - | May 7, 15:15 UTC | May 7, 16:45 UTC | 1h 30m |
| 2026-05-01 | EVAL75 | - | May 1, 14:55 UTC | May 1, 16:20 UTC | 1h 25m |
| 2026-04-29 | EVAL00 | - | Apr 29, 20:15 UTC | Apr 29, 21:30 UTC | 1h 15m |
| 2026-04-28 | EVAL75 | - | Apr 28, 01:05 UTC | Apr 28, 02:00 UTC | 55m |
| 2026-04-27 | EVAL75 | - | Apr 27, 22:10 UTC | Apr 27, 23:45 UTC | 1h 35m |
| 2026-04-24 | EVAL43 | - | Apr 24, 16:35 UTC | Apr 24, 18:05 UTC | 1h 30m |
| 2026-04-23 | EVAL59 | HUA → HUA | Apr 23, 18:40 UTC | Apr 23, 19:40 UTC | 1h 0m |
| 2026-04-23 | EVAL18 | - | Apr 23, 16:10 UTC | Apr 23, 17:40 UTC | 1h 29m |
| 2026-04-22 | EVAL59 | - | Apr 22, 18:40 UTC | Apr 22, 19:55 UTC | 1h 15m |
| 2026-04-22 | EVAL09 | - | Apr 22, 15:00 UTC | Apr 22, 16:25 UTC | 1h 25m |
| 2026-04-21 | EVAL75 | - | Apr 21, 21:05 UTC | Apr 21, 22:05 UTC | 1h 0m |
| 2026-04-20 | EVAL99 | - | Apr 20, 20:00 UTC | Apr 20, 21:20 UTC | 1h 20m |
| 2026-04-20 | EVAL99 | - | Apr 20, 16:40 UTC | Apr 20, 17:45 UTC | 1h 5m |
| 2026-04-20 | EVAL63 | - | Apr 20, 12:55 UTC | Apr 20, 14:25 UTC | 1h 30m |
| 2026-04-17 | EVAL09 | - | Apr 17, 15:20 UTC | Apr 17, 16:15 UTC | 55m |
| 2026-04-17 | EVAL09 | - | Apr 17, 14:45 UTC | Apr 17, 15:15 UTC | 29m |
| 2026-04-16 | EVAL59 | - | Apr 16, 15:15 UTC | Apr 16, 15:55 UTC | 40m |
| 2026-04-16 | EVAL59 | - | Apr 16, 14:55 UTC | Apr 16, 15:10 UTC | 15m |
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 14-00066 page for operator, model, and routing details .