sensors Mode-S transponder
AE4EE3
ICAO 24-bit transponder address
Currently assigned to 11-0120 · Cirrus T-53A Kaydet II
- Hex
- AE4EE3
- Octal
- 53447343
- Decimal
- 11,423,459
- Tail
- 11-0120
- Type
- SR20
- Flights observed
- 31
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 4h ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SHARK60 | - | 31 | 2026-07-14 |
Recent flights last 31
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SHARK60 | - | Jul 14, 16:35 UTC | Jul 14, 17:40 UTC | 1h 5m |
| 2026-07-14 | SHARK60 | - | Jul 14, 15:05 UTC | Jul 14, 15:25 UTC | 20m |
| 2026-07-14 | SHARK60 | - | Jul 14, 13:45 UTC | Jul 14, 14:30 UTC | 45m |
| 2026-07-13 | SHARK60 | - | Jul 13, 14:45 UTC | Jul 13, 15:05 UTC | 20m |
| 2026-07-13 | SHARK60 | - | Jul 13, 13:30 UTC | Jul 13, 13:45 UTC | 15m |
| 2026-07-10 | SHARK60 | - | Jul 10, 16:25 UTC | Jul 10, 17:45 UTC | 1h 20m |
| 2026-07-10 | SHARK60 | - | Jul 10, 13:45 UTC | Jul 10, 15:05 UTC | 1h 20m |
| 2026-07-09 | SHARK60 | - | Jul 9, 16:25 UTC | Jul 9, 17:55 UTC | 1h 30m |
| 2026-07-09 | SHARK60 | AFF → BJC | Jul 9, 13:45 UTC | Jul 9, 15:30 UTC | 1h 45m |
| 2026-07-08 | SHARK60 | - | Jul 8, 15:45 UTC | Jul 8, 16:40 UTC | 55m |
| 2026-07-06 | SHARK60 | - | Jul 6, 15:55 UTC | Jul 6, 17:15 UTC | 1h 20m |
| 2026-07-06 | SHARK60 | - | Jul 6, 13:45 UTC | Jul 6, 14:55 UTC | 1h 10m |
| 2026-07-02 | SHARK60 | - | Jul 2, 16:35 UTC | Jul 2, 17:25 UTC | 50m |
| 2026-07-02 | SHARK60 | - | Jul 2, 14:50 UTC | Jul 2, 15:55 UTC | 1h 5m |
| 2026-07-01 | SHARK60 | - | Jul 1, 16:45 UTC | Jul 1, 17:55 UTC | 1h 10m |
| 2026-07-01 | SHARK60 | - | Jul 1, 13:45 UTC | Jul 1, 14:40 UTC | 55m |
| 2026-06-30 | SHARK60 | - | Jun 30, 18:55 UTC | Jun 30, 19:55 UTC | 1h 0m |
| 2026-06-30 | SHARK60 | - | Jun 30, 16:10 UTC | Jun 30, 17:15 UTC | 1h 5m |
| 2026-06-26 | SHARK60 | - | Jun 26, 14:29 UTC | Jun 26, 15:54 UTC | 1h 25m |
| 2026-06-25 | SHARK60 | - | Jun 25, 16:09 UTC | Jun 25, 17:25 UTC | 1h 15m |
| 2026-06-23 | SHARK60 | - | Jun 23, 18:34 UTC | Jun 23, 19:44 UTC | 1h 10m |
| 2026-06-23 | SHARK60 | - | Jun 23, 13:50 UTC | Jun 23, 15:24 UTC | 1h 35m |
| 2026-06-11 | SHARK60 | - | Jun 11, 18:05 UTC | Jun 11, 19:10 UTC | 1h 5m |
| 2026-06-11 | SHARK60 | - | Jun 11, 14:00 UTC | Jun 11, 14:10 UTC | 10m |
| 2026-06-11 | SHARK60 | - | Jun 11, 12:35 UTC | Jun 11, 13:20 UTC | 45m |
| 2026-06-10 | SHARK60 | - | Jun 10, 15:15 UTC | Jun 10, 17:15 UTC | 2h 0m |
| 2026-06-10 | SHARK60 | - | Jun 10, 12:30 UTC | Jun 10, 13:15 UTC | 45m |
| 2026-06-09 | SHARK60 | - | Jun 9, 14:40 UTC | Jun 9, 15:15 UTC | 35m |
| 2026-06-04 | SHARK60 | - | Jun 4, 16:10 UTC | Jun 4, 17:30 UTC | 1h 20m |
| 2026-06-04 | SHARK60 | - | Jun 4, 12:55 UTC | Jun 4, 14:35 UTC | 1h 40m |
| 2026-05-08 | SHARK60 | - | May 8, 20:00 UTC | May 8, 20:50 UTC | 50m |
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 11-0120 page for operator, model, and routing details .