sensors Mode-S transponder
AE3302
ICAO 24-bit transponder address
- Hex
- AE3302
- Octal
- 53431402
- Decimal
- 11,416,322
No current signal · last broadcast 1d ago
- Flights observed
- 43
- Distinct callsigns
- 16
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAKAL01 | - | 10 | 2026-04-16 |
| ZORRO91 | - | 7 | 2026-05-14 |
| ZORRO77 | - | 6 | 2026-05-28 |
| ZORRO75 | - | 3 | 2026-04-30 |
| ZORRO43 | - | 3 | 2026-05-14 |
| JAKAL67 | - | 3 | 2026-04-17 |
| ZORRO55 | - | 2 | 2026-05-11 |
| ZORRO90 | - | 1 | 2026-05-12 |
| ZORRO67 | - | 1 | 2026-05-07 |
| ZORRO39 | - | 1 | 2026-05-14 |
| ZORRO31 | - | 1 | 2026-05-13 |
| ZORRO28 | - | 1 | 2026-05-07 |
| ZORRO2 | - | 1 | 2026-05-12 |
| ZORRO15 | - | 1 | 2026-04-29 |
| ZORRO02 | - | 1 | 2026-05-11 |
| JAKAL23 | - | 1 | 2026-04-13 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | ZORRO77 | OKC → OKC | May 28, 21:15 UTC | May 28, 23:10 UTC | 1h 55m |
| 2026-05-28 | ZORRO77 | OKC → OKC | May 28, 16:55 UTC | May 28, 18:55 UTC | 2h 0m |
| 2026-05-26 | ZORRO77 | - | May 26, 21:09 UTC | May 26, 23:05 UTC | 1h 55m |
| 2026-05-26 | ZORRO77 | - | May 26, 16:05 UTC | May 26, 18:05 UTC | 2h 0m |
| 2026-05-14 | ZORRO91 | - | May 14, 20:50 UTC | May 14, 22:50 UTC | 2h 0m |
| 2026-05-14 | ZORRO39 | OKC → OKC | May 14, 16:35 UTC | May 14, 18:55 UTC | 2h 20m |
| 2026-05-14 | ZORRO43 | OKC → OKC | May 14, 01:45 UTC | May 14, 03:30 UTC | 1h 45m |
| 2026-05-13 | ZORRO43 | - | May 13, 21:00 UTC | May 13, 22:50 UTC | 1h 50m |
| 2026-05-13 | ZORRO31 | OKC → OKC | May 13, 16:15 UTC | May 13, 18:15 UTC | 2h 0m |
| 2026-05-13 | ZORRO43 | OKC → OKC | May 13, 01:20 UTC | May 13, 03:05 UTC | 1h 45m |
| 2026-05-12 | ZORRO90 | - | May 12, 21:10 UTC | May 12, 23:20 UTC | 2h 10m |
| 2026-05-12 | ZORRO2 | - | May 12, 16:15 UTC | May 12, 18:10 UTC | 1h 55m |
| 2026-05-11 | ZORRO55 | - | May 11, 21:15 UTC | May 11, 22:35 UTC | 1h 19m |
| 2026-05-11 | ZORRO02 | OKC → OKC | May 11, 17:10 UTC | May 11, 18:55 UTC | 1h 45m |
| 2026-05-07 | ZORRO67 | OKC → OKC | May 7, 20:05 UTC | May 7, 21:50 UTC | 1h 45m |
| 2026-05-07 | ZORRO91 | - | May 7, 14:15 UTC | May 7, 15:10 UTC | 55m |
| 2026-05-07 | ZORRO28 | OKC → OKC | May 7, 01:55 UTC | May 7, 03:25 UTC | 1h 30m |
| 2026-05-05 | ZORRO91 | OKC → OKC | May 5, 14:10 UTC | May 5, 14:35 UTC | 25m |
| 2026-05-04 | ZORRO91 | OKC → OKC | May 4, 20:55 UTC | May 4, 22:45 UTC | 1h 50m |
| 2026-05-04 | ZORRO91 | OKC → OKC | May 4, 16:15 UTC | May 4, 18:10 UTC | 1h 55m |
| 2026-05-01 | ZORRO77 | OKC → OKC | May 1, 16:35 UTC | May 1, 18:40 UTC | 2h 5m |
| 2026-04-30 | ZORRO75 | OKC → OKC | Apr 30, 21:05 UTC | Apr 30, 23:10 UTC | 2h 5m |
| 2026-04-30 | ZORRO75 | OKC → OKC | Apr 30, 16:00 UTC | Apr 30, 18:10 UTC | 2h 10m |
| 2026-04-29 | ZORRO15 | - | Apr 29, 21:00 UTC | Apr 29, 23:00 UTC | 2h 0m |
| 2026-04-29 | ZORRO91 | OKC → OKC | Apr 29, 16:05 UTC | Apr 29, 18:10 UTC | 2h 5m |
| 2026-04-27 | ZORRO91 | OKC → OKC | Apr 27, 16:55 UTC | Apr 27, 18:55 UTC | 2h 0m |
| 2026-04-24 | ZORRO77 | OKC → OKC | Apr 24, 15:40 UTC | Apr 24, 17:45 UTC | 2h 5m |
| 2026-04-20 | ZORRO75 | OKC → OKC | Apr 20, 20:30 UTC | Apr 20, 22:35 UTC | 2h 5m |
| 2026-04-20 | ZORRO55 | - | Apr 20, 15:25 UTC | Apr 20, 17:35 UTC | 2h 10m |
| 2026-04-17 | JAKAL67 | - | Apr 17, 01:20 UTC | Apr 17, 02:25 UTC | 1h 5m |
| 2026-04-17 | JAKAL67 | - | Apr 17, 00:30 UTC | Apr 17, 01:15 UTC | 45m |
| 2026-04-16 | JAKAL67 | - | Apr 16, 17:30 UTC | Apr 16, 19:10 UTC | 1h 40m |
| 2026-04-16 | JAKAL01 | - | Apr 16, 03:09 UTC | Apr 16, 03:19 UTC | 10m |
| 2026-04-16 | JAKAL01 | - | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-16 | JAKAL01 | - | Apr 16, 00:45 UTC | Apr 16, 01:05 UTC | 20m |
| 2026-04-15 | JAKAL01 | - | Apr 15, 23:10 UTC | Apr 15, 23:55 UTC | 45m |
| 2026-04-15 | JAKAL01 | - | Apr 15, 21:05 UTC | Apr 15, 23:00 UTC | 1h 55m |
| 2026-04-15 | JAKAL01 | - | Apr 15, 02:55 UTC | Apr 15, 04:10 UTC | 1h 15m |
| 2026-04-15 | JAKAL01 | - | Apr 15, 00:55 UTC | Apr 15, 02:50 UTC | 1h 55m |
| 2026-04-14 | JAKAL01 | - | Apr 14, 22:55 UTC | Apr 15, 00:00 UTC | 1h 5m |
| 2026-04-14 | JAKAL01 | - | Apr 14, 20:55 UTC | Apr 14, 22:50 UTC | 1h 55m |
| 2026-04-14 | JAKAL01 | - | Apr 14, 20:35 UTC | Apr 14, 20:50 UTC | 15m |
| 2026-04-13 | JAKAL23 | - | Apr 13, 14:20 UTC | Apr 13, 14:30 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.
Mode-S AE3302 frequently asked
What is Mode-S code AE3302?
AE3302 is an ICAO 24-bit transponder address.
Is AE3302 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AE3302, octal 53431402, decimal 11,416,322.