Departure (F39224 Flight Schedule)
Jeddah, Saudi Arabia+03 00:00:00 DAY
Arrival (F39224 Flight Schedule)
Tashkent, Uzbekistan+05 00:00:00 DAY
Flight Radar Checker F39224
Live Flight Tracker Map
Flight F39224 from Jeddah to Tashkent is operated by Unknown. Scheduled time of departure from King Abdulaziz Intl is 16:10 +03 and scheduled time of arrival in Yuzhny is 22:45 +05. The duration of the flight is 4 hours 35 minutes.
Not Rated
Flight Finder
from Tashkent to Jeddah
| Flight | Departure | Arrival |
|---|---|---|
| HH507 00:40 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HH509 00:50 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| F39225 02:00 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HH501 02:10 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| F39223 03:50 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| F39331 12:50 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HY337 13:10 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HH503 15:30 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| XY634 19:55 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HY335 22:00 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
| HH505 23:10 |
Yuzhny (TAS) |
King Abdulaziz Intl (JED) |
History Flight Information for F39224 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Fri, 21 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:10 +03 | 22:45 +05 | |||
| Thu, 20 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:15 +03 | 22:50 +05 | |||
| Wed, 19 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 14:25 +03 | 21:00 +05 | |||
| Tue, 18 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:10 +03 | 22:45 +05 | |||
| Mon, 17 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:25 +03 | 23:00 +05 | |||
| Sun, 16 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:30 +03 | 23:05 +05 | |||
| Sat, 15 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 18:50 +03 | 01:25 +05 | |||
| Fri, 14 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:10 +03 | 22:45 +05 | |||
| Thu, 13 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:15 +03 | 22:50 +05 | |||
| Wed, 12 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 18:20 +03 | 00:55 +05 | |||
| Tue, 11 Feb | F39224 | King Abdulaziz Intl (JED) | King Abdulaziz Intl (JED) | 16:10 +03 | 22:45 +03 | |||
| Mon, 10 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:15 +03 | 22:50 +05 | |||
| Sun, 09 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 15:55 +03 | 22:30 +05 | |||
| Sat, 08 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 17:45 +03 | 00:20 +05 | |||
| Fri, 07 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:10 +03 | 22:45 +05 | |||
| Thu, 06 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:15 +03 | 22:50 +05 | |||
| Wed, 05 Feb | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 16:15 +03 | 22:50 +05 | |||
| Fri, 31 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 17:20 +03 | 23:55 +05 | |||
| Thu, 30 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 13:30 +03 | 20:05 +05 | |||
| Wed, 29 Jan | F39224 | King Abdulaziz Intl (JED) | King Abdulaziz Intl (JED) | 19:00 +03 | 01:35 +03 | |||
| Tue, 28 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 18:25 +03 | 01:00 +05 | |||
| Mon, 27 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 14:55 +03 | 21:30 +05 | |||
| Sun, 26 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 17:15 +03 | 23:50 +05 | |||
| Sat, 25 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 15:15 +03 | 21:50 +05 | |||
| Fri, 24 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 17:30 +03 | 00:05 +05 | |||
| Thu, 23 Jan | F39224 | King Abdulaziz Intl (JED) | Yuzhny (TAS) | 15:15 +03 | 21:50 +05 | |||
Disclaimer for F39224 Flight Radar Data
Flight F39224 from King Abdulaziz Intl to Yuzhny data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight F39224 data.
