sensors Mode-S transponder
AE4A12
ICAO 24-bit transponder address
Currently assigned to 166137 · Raytheon T-6B Texan II
- Hex
- AE4A12
- Octal
- 53445022
- Decimal
- 11,422,226
- Tail
- 166137
- Type
- TEX2
- Flights observed
- 30
- Distinct callsigns
- 7
- Country
- -
- Last broadcast
- 8h ago
Last known position
Callsign history 7 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | BB137 | - | Jul 15, 00:35 UTC | Jul 15, 01:45 UTC | 1h 10m |
| 2026-07-14 | RN137 | - | Jul 14, 17:00 UTC | Jul 14, 17:35 UTC | 35m |
| 2026-07-14 | RN137 | - | Jul 14, 14:25 UTC | Jul 14, 14:50 UTC | 25m |
| 2026-07-13 | BB137 | - | Jul 13, 17:45 UTC | Jul 13, 18:25 UTC | 40m |
| 2026-07-13 | BB137 | - | Jul 13, 14:15 UTC | Jul 13, 15:05 UTC | 50m |
| 2026-07-11 | BB137 | - | Jul 11, 23:20 UTC | Jul 12, 00:15 UTC | 55m |
| 2026-07-11 | BB137 | - | Jul 11, 20:35 UTC | Jul 11, 21:40 UTC | 1h 5m |
| 2026-07-10 | SH137Z | - | Jul 10, 16:45 UTC | Jul 10, 17:10 UTC | 25m |
| 2026-07-09 | RN137 | - | Jul 9, 00:55 UTC | Jul 9, 02:25 UTC | 1h 30m |
| 2026-07-08 | RN137 | - | Jul 8, 21:10 UTC | Jul 8, 22:35 UTC | 1h 25m |
| 2026-06-15 | RN137 | - | Jun 15, 19:50 UTC | Jun 15, 20:00 UTC | 10m |
| 2026-06-15 | RN137 | - | Jun 15, 18:29 UTC | Jun 15, 19:14 UTC | 45m |
| 2026-06-15 | RN137 | - | Jun 15, 15:30 UTC | Jun 15, 16:09 UTC | 40m |
| 2026-06-12 | BB137 | - | Jun 12, 17:35 UTC | Jun 12, 19:00 UTC | 1h 25m |
| 2026-06-12 | BB137 | - | Jun 12, 14:20 UTC | Jun 12, 15:10 UTC | 50m |
| 2026-06-12 | RN137 | - | Jun 12, 00:55 UTC | Jun 12, 02:35 UTC | 1h 40m |
| 2026-06-11 | RN137 | - | Jun 11, 21:55 UTC | Jun 11, 23:15 UTC | 1h 20m |
| 2026-06-11 | SH137 | - | Jun 11, 16:20 UTC | Jun 11, 16:50 UTC | 30m |
| 2026-06-11 | SH137 | - | Jun 11, 13:05 UTC | Jun 11, 14:20 UTC | 1h 15m |
| 2026-06-10 | SH081 | - | Jun 10, 21:55 UTC | Jun 10, 22:20 UTC | 25m |
| 2026-06-10 | SH137 | - | Jun 10, 14:30 UTC | Jun 10, 15:00 UTC | 30m |
| 2026-06-09 | RN137 | - | Jun 9, 17:40 UTC | Jun 9, 18:10 UTC | 30m |
| 2026-06-09 | RN137 | - | Jun 9, 13:15 UTC | Jun 9, 13:50 UTC | 35m |
| 2026-06-08 | TXN137 | - | Jun 8, 19:30 UTC | Jun 8, 19:50 UTC | 20m |
| 2026-06-08 | TXN137 | - | Jun 8, 16:20 UTC | Jun 8, 17:00 UTC | 40m |
| 2026-06-05 | RN137 | - | Jun 5, 20:05 UTC | Jun 5, 20:55 UTC | 50m |
| 2026-06-05 | RN137 | - | Jun 5, 16:50 UTC | Jun 5, 17:20 UTC | 30m |
| 2026-06-05 | MX137 | SYR → TPA | Jun 5, 13:25 UTC | Jun 5, 14:00 UTC | 35m |
| 2026-06-02 | MX137 | SYR → TPA | Jun 2, 13:45 UTC | Jun 2, 14:15 UTC | 30m |
| 2026-05-29 | MX137 | SYR → TPA | May 29, 13:55 UTC | May 29, 14:05 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 166137 page for operator, model, and routing details .