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