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