Not currently tracked · last seen 12h ago
- Flights observed
- 72 showing last 50
- Avg flight time
- 4h 18m
- Typical route
- MED → CAI
- Last seen
- 12h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | JNB → CAI | May 29, 19:55 UTC | May 29, 23:15 UTC | 3h 20m |
| 2026-05-29 | CAI → JNB | May 29, 04:30 UTC | May 29, 05:00 UTC | 30m |
| 2026-05-27 | JNB → CAI | May 27, 21:40 UTC | May 28, 05:15 UTC | 7h 35m |
| 2026-05-26 | DOH → CAI | May 26, 07:45 UTC | May 26, 14:24 UTC | 6h 40m |
| 2026-05-25 | JNB → CAI | May 25, 19:54 UTC | May 26, 03:25 UTC | 7h 30m |
| 2026-05-24 | CAI → JNB | May 24, 21:05 UTC | May 24, 21:15 UTC | 10m |
| 2026-05-24 | RUH → CAI | May 24, 07:05 UTC | May 24, 12:45 UTC | 5h 40m |
| 2026-05-22 | MXP → CAI | May 22, 14:10 UTC | May 22, 17:10 UTC | 3h 0m |
| 2026-05-22 | CAI → MXP | May 22, 08:00 UTC | May 22, 11:15 UTC | 3h 15m |
| 2026-05-21 | JED → CAI | May 21, 14:40 UTC | May 21, 22:35 UTC | 7h 55m |
| 2026-05-20 | DMM → CAI | May 20, 20:10 UTC | May 20, 20:35 UTC | 25m |
| 2026-05-20 | MED → CAI | May 20, 10:15 UTC | May 20, 10:35 UTC | 20m |
| 2026-05-19 | JED → CAI | May 19, 22:15 UTC | May 20, 03:05 UTC | 4h 50m |
| 2026-05-19 | JED → CAI | May 19, 17:05 UTC | May 19, 17:25 UTC | 20m |
| 2026-05-19 | CAI → MED | May 19, 06:05 UTC | May 19, 09:35 UTC | 3h 30m |
| 2026-05-18 | MED → CAI | May 18, 23:40 UTC | May 19, 03:45 UTC | 4h 5m |
| 2026-05-18 | MED → CAI | May 18, 18:50 UTC | May 18, 19:25 UTC | 35m |
| 2026-05-18 | - | May 18, 12:20 UTC | May 18, 12:35 UTC | 15m |
| 2026-05-17 | - | May 17, 14:30 UTC | May 18, 06:25 UTC | 15h 55m |
| 2026-05-17 | - | May 17, 07:45 UTC | May 18, 06:25 UTC | 22h 40m |
| 2026-05-16 | MED → CAI | May 16, 10:05 UTC | May 16, 10:25 UTC | 20m |
| 2026-05-15 | JED → CAI | May 15, 21:45 UTC | May 16, 02:15 UTC | 4h 30m |
| 2026-05-15 | MED → CAI | May 15, 14:50 UTC | May 15, 18:50 UTC | 4h 0m |
| 2026-05-15 | MED → CAI | May 15, 09:45 UTC | May 15, 10:10 UTC | 25m |
| 2026-05-15 | MED → CAI | May 15, 00:40 UTC | May 15, 00:50 UTC | 10m |
| 2026-05-14 | MED → CAI | May 14, 09:50 UTC | May 14, 18:10 UTC | 8h 20m |
| 2026-05-13 | JED → CAI | May 13, 19:30 UTC | May 13, 19:50 UTC | 20m |
| 2026-05-13 | MED → CAI | May 13, 05:10 UTC | May 13, 09:10 UTC | 4h 0m |
| 2026-05-12 | MED → CAI | May 12, 14:10 UTC | May 12, 21:25 UTC | 7h 15m |
| 2026-05-11 | MED → CAI | May 11, 07:40 UTC | May 11, 19:10 UTC | 11h 30m |
| 2026-05-10 | JED → HBE | May 10, 19:00 UTC | May 10, 19:19 UTC | 20m |
| 2026-05-10 | - | May 10, 05:50 UTC | May 10, 06:04 UTC | 15m |
| 2026-05-09 | MED → CAI | May 9, 15:10 UTC | May 9, 19:35 UTC | 4h 25m |
| 2026-05-09 | MED → CAI | May 9, 06:20 UTC | May 9, 10:10 UTC | 3h 50m |
| 2026-05-08 | JNB → CAI | May 8, 20:05 UTC | May 8, 23:35 UTC | 3h 30m |
| 2026-05-08 | CAI → JNB | May 8, 04:39 UTC | May 8, 05:14 UTC | 35m |
| 2026-05-06 | DXB → CAI | May 6, 16:00 UTC | May 6, 16:15 UTC | 15m |
| 2026-05-06 | CAI → MED | May 6, 00:01 UTC | May 6, 03:35 UTC | 3h 35m |
| 2026-05-04 | MXP → CAI | May 4, 14:20 UTC | May 4, 17:15 UTC | 2h 55m |
| 2026-05-03 | CAI → MXP | May 3, 19:50 UTC | May 4, 11:45 UTC | 15h 55m |
| 2026-05-03 | CAI → JNB | May 3, 04:20 UTC | May 3, 04:50 UTC | 30m |
| 2026-05-02 | AUH → CAI | May 2, 13:50 UTC | May 2, 17:20 UTC | 3h 30m |
| 2026-05-02 | CAI → AUH | May 2, 10:35 UTC | May 2, 11:25 UTC | 50m |
| 2026-05-01 | AUH → CAI | May 1, 13:45 UTC | May 1, 17:25 UTC | 3h 40m |
| 2026-05-01 | CAI → AUH | May 1, 10:40 UTC | May 1, 11:35 UTC | 55m |
| 2026-04-30 | BOM → CAI | Apr 30, 23:05 UTC | May 1, 04:40 UTC | 5h 35m |
| 2026-04-30 | CAI → BOM | Apr 30, 17:50 UTC | Apr 30, 20:50 UTC | 3h 0m |
| 2026-04-30 | RUH → CAI | Apr 30, 12:30 UTC | Apr 30, 12:55 UTC | 25m |
| 2026-04-26 | JNB → CAI | Apr 26, 19:50 UTC | Apr 26, 23:15 UTC | 3h 25m |
| 2026-04-25 | MAD → LXR | Apr 25, 12:50 UTC | Apr 26, 07:00 UTC | 18h 10m |
Specifications
| Registration | SU-GDT |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 01015C · 00200534 (octal) |
Looking for transponder-level data? View the Mode-S 01015C page for country allocation, callsign history, and ADS-B signal details.
SU-GDT frequently asked
What type of aircraft is SU-GDT?
SU-GDT is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for SU-GDT?
SU-GDT broadcasts on Mode-S (ICAO 24-bit) address 01015C (octal 00200534). View the transponder page.
What route does SU-GDT typically fly?
SU-GDT most frequently flies between MED and CAI based on observed flights.
Where is SU-GDT right now?
SU-GDT is not currently being tracked; last seen 12h ago.