Not currently tracked · last seen 2h ago
- Flights observed
- 144 showing last 50
- Avg flight time
- 2h 36m
- Typical route
- SAW → CAI
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-11 | MCT → CAI | Jun 11, 05:45 UTC | Jun 11, 14:20 UTC | 8h 35m |
| 2026-06-10 | GIZ → CAI | Jun 10, 20:35 UTC | Jun 11, 02:30 UTC | 5h 55m |
| 2026-06-10 | TIF → CAI | Jun 10, 18:45 UTC | Jun 10, 19:25 UTC | 40m |
| 2026-06-10 | CAI → DMM | Jun 10, 00:15 UTC | Jun 10, 00:30 UTC | 15m |
| 2026-06-09 | SAW → CAI | Jun 9, 12:50 UTC | Jun 9, 14:45 UTC | 1h 55m |
| 2026-06-09 | CAI → SAW | Jun 9, 10:00 UTC | Jun 9, 11:35 UTC | 1h 35m |
| 2026-06-09 | JED → CAI | Jun 9, 07:40 UTC | Jun 9, 07:55 UTC | 15m |
| 2026-06-08 | BGY → CAI | Jun 8, 20:25 UTC | Jun 8, 23:30 UTC | 3h 5m |
| 2026-06-08 | CAI → BGY | Jun 8, 15:25 UTC | Jun 8, 18:55 UTC | 3h 30m |
| 2026-06-08 | TUU → CAI | Jun 8, 12:30 UTC | Jun 8, 12:40 UTC | 10m |
| 2026-06-07 | GIZ → CAI | Jun 7, 22:15 UTC | Jun 7, 22:45 UTC | 30m |
| 2026-06-07 | CAI → RUH | Jun 7, 09:25 UTC | Jun 7, 14:55 UTC | 5h 30m |
| 2026-06-06 | CAI → RUH | Jun 6, 22:34 UTC | Jun 7, 04:05 UTC | 5h 30m |
| 2026-06-06 | - | Jun 6, 14:30 UTC | Jun 6, 19:04 UTC | 4h 35m |
| 2026-06-06 | SAW → CAI | Jun 6, 11:19 UTC | Jun 6, 12:45 UTC | 1h 25m |
| 2026-06-06 | CAI → SAW | Jun 6, 08:10 UTC | Jun 6, 09:50 UTC | 1h 40m |
| 2026-06-06 | DMM → CAI | Jun 6, 04:15 UTC | Jun 6, 04:35 UTC | 20m |
| 2026-06-05 | CAI → DMM | Jun 5, 22:55 UTC | Jun 5, 23:05 UTC | 10m |
| 2026-06-05 | CAI → RUH | Jun 5, 09:50 UTC | Jun 5, 15:15 UTC | 5h 25m |
| 2026-06-05 | JED → CAI | Jun 5, 07:50 UTC | Jun 5, 08:05 UTC | 15m |
| 2026-06-04 | AHB → CAI | Jun 4, 22:30 UTC | Jun 4, 22:50 UTC | 20m |
| 2026-06-04 | SAW → CAI | Jun 4, 14:10 UTC | Jun 4, 15:55 UTC | 1h 45m |
| 2026-06-04 | CAI → SAW | Jun 4, 11:20 UTC | Jun 4, 12:55 UTC | 1h 35m |
| 2026-06-04 | JED → CAI | Jun 4, 08:40 UTC | Jun 4, 08:50 UTC | 10m |
| 2026-06-04 | GIZ → CAI | Jun 4, 02:10 UTC | Jun 4, 02:20 UTC | 10m |
| 2026-06-03 | TIF → CAI | Jun 3, 18:35 UTC | Jun 3, 18:50 UTC | 15m |
| 2026-06-03 | JED → CAI | Jun 3, 11:55 UTC | Jun 3, 12:10 UTC | 15m |
| 2026-06-03 | DMM → CAI | Jun 3, 05:05 UTC | Jun 3, 05:25 UTC | 20m |
| 2026-06-02 | CAI → RUH | Jun 2, 09:10 UTC | Jun 2, 14:35 UTC | 5h 25m |
| 2026-06-01 | BGY → CAI | Jun 1, 21:15 UTC | Jun 2, 00:25 UTC | 3h 10m |
| 2026-06-01 | CAI → BGY | Jun 1, 16:05 UTC | Jun 1, 19:30 UTC | 3h 25m |
| 2026-06-01 | BGY → CAI | Jun 1, 11:10 UTC | Jun 1, 14:15 UTC | 3h 5m |
| 2026-06-01 | CAI → BGY | Jun 1, 06:20 UTC | Jun 1, 09:55 UTC | 3h 35m |
| 2026-06-01 | HAS → CAI | Jun 1, 01:05 UTC | Jun 1, 05:10 UTC | 4h 5m |
| 2026-05-31 | GIZ → CAI | May 31, 22:35 UTC | May 31, 23:15 UTC | 40m |
| 2026-05-31 | CAI → RUH | May 31, 10:25 UTC | May 31, 15:55 UTC | 5h 30m |
| 2026-05-31 | JED → CAI | May 31, 08:25 UTC | May 31, 08:40 UTC | 15m |
| 2026-05-30 | RUH → CAI | May 30, 13:35 UTC | May 30, 19:15 UTC | 5h 40m |
| 2026-05-30 | SAW → CAI | May 30, 10:25 UTC | May 30, 11:55 UTC | 1h 30m |
| 2026-05-30 | CAI → SAW | May 30, 07:05 UTC | May 30, 08:55 UTC | 1h 50m |
| 2026-05-29 | DMM → CAI | May 29, 22:40 UTC | May 30, 04:50 UTC | 6h 10m |
| 2026-05-29 | AHB → CAI | May 29, 20:35 UTC | May 29, 20:55 UTC | 20m |
| 2026-05-29 | CAI → AHB | May 29, 15:20 UTC | May 29, 15:30 UTC | 10m |
| 2026-05-29 | BGY → CAI | May 29, 10:25 UTC | May 29, 13:35 UTC | 3h 10m |
| 2026-05-29 | CAI → BGY | May 29, 05:35 UTC | May 29, 08:50 UTC | 3h 15m |
| 2026-05-28 | DMM → CAI | May 28, 21:25 UTC | May 29, 03:25 UTC | 6h 0m |
| 2026-05-28 | HAS → CAI | May 28, 15:55 UTC | May 28, 19:45 UTC | 3h 50m |
| 2026-05-28 | SAW → CAI | May 28, 12:40 UTC | May 28, 14:05 UTC | 1h 25m |
| 2026-05-28 | CAI → SAW | May 28, 03:10 UTC | May 28, 11:05 UTC | 7h 55m |
| 2026-05-27 | BGY → CAI | May 27, 20:10 UTC | May 27, 23:20 UTC | 3h 10m |
Specifications
| Registration | SU-AAE |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 0101E1 · 00200741 (octal) |
Looking for transponder-level data? View the Mode-S 0101E1 page for country allocation, callsign history, and ADS-B signal details.
SU-AAE frequently asked
What type of aircraft is SU-AAE?
SU-AAE is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for SU-AAE?
SU-AAE broadcasts on Mode-S (ICAO 24-bit) address 0101E1 (octal 00200741). View the transponder page.
What route does SU-AAE typically fly?
SU-AAE most frequently flies between SAW and CAI based on observed flights.
Where is SU-AAE right now?
SU-AAE is not currently being tracked; last seen 2h ago.