| ARRIVED 86 HOUR 45 MINUTES AGO |
 |  |
Departure (3O352 Flight Schedule)
Toulouse, FranceCEST 00:00:00 DAY
Arrival (3O352 Flight Schedule)
Fes, Morocco+01 00:00:00 DAY
Flight Radar Checker E5 352
Live Flight Tracker Map
Flight 3O352 from Toulouse to Fes is operated by Air Arabia Maroc. Scheduled time of departure from Blagnac is 09:50 CEST and scheduled time of arrival in Saiss is 10:50 +01. The duration of the flight is 2 hours 0 minute.
History Flight Information for 3O352 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Wed, 06 May | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | |||
| Sat, 02 May | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | CN-NML ( A320) | 09:46 CEST | 10:30 +01 |
| Wed, 29 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | CN-NML ( A320) | 10:06 CEST | 10:46 +01 |
| Sat, 25 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | CN-NML ( A320) | 10:03 CEST | 10:36 +01 |
| Wed, 22 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | CN-NML ( A320) | 10:21 CEST | 10:48 +01 |
| Sat, 18 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | CN-NML ( A320) | 10:01 CEST | 10:27 +01 |
| Wed, 15 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | 10:16 CEST | 10:34 +01 | |
| Sat, 11 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | 10:00 CEST | 10:30 +01 | |
| Wed, 08 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | 09:58 CEST | 10:31 +01 | |
| Sat, 04 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | 10:06 CEST | 10:29 +01 | |
| Wed, 01 Apr | 3O352 | Blagnac (TLS) | Saiss (FEZ) | 09:50 CEST | 10:50 +01 | 10:02 CEST | 10:20 +01 | |
Disclaimer for 3O352 Flight Radar Data
Flight 3O352 from Blagnac to Saiss 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 3O352 data.
