| ARRIVED 32 HOUR 45 MINUTES AGO |
 |  |
Departure (3O351 Flight Schedule)
Fes, Morocco+00 00:00:00 DAY
Arrival (3O351 Flight Schedule)
Toulouse, FranceCET 00:00:00 DAY
Flight Radar Checker E5 351
Live Flight Tracker Map
Flight 3O351 from Fes to Toulouse is operated by Air Arabia Maroc. Scheduled time of departure from Saiss is 17:00 +00 and scheduled time of arrival in Blagnac is 20:05 CET. The duration of the flight is 2 hours 5 minutes.
History Flight Information for 3O351 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Wed, 05 Mar | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 17:00 +00 | 20:05 CET | CN-NML ( A320) | 17:38 +00 | 19:58 CET |
| Sat, 01 Mar | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 12:05 +00 | 15:10 CET | CN-NMJ (Airbus A320) | 12:51 +00 | 15:18 CET |
| Wed, 26 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 17:00 +00 | 20:05 CET | CN-NMH (Airbus A320) | 17:44 +00 | 20:14 CET |
| Sat, 22 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 13:05 +01 | 15:10 CET | CN-NMJ (Airbus A320) | 12:37 +01 | 15:01 CET |
| Wed, 19 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 18:00 +01 | 20:05 CET | CN-NMJ (Airbus A320) | 17:17 +01 | 19:50 CET |
| Sat, 15 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 13:05 +01 | 15:10 CET | CN-NMJ (Airbus A320) | 12:33 +01 | 15:01 CET |
| Wed, 12 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 18:00 +01 | 20:05 CET | CN-NMJ (Airbus A320) | 17:30 +01 | 20:05 CET |
| Sat, 08 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 13:05 +01 | 15:10 CET | CN-NMJ (Airbus A320) | 13:01 +01 | 15:35 CET |
| Wed, 05 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 18:00 +01 | 20:05 CET | 17:23 +01 | 19:57 CET | |
| Sat, 01 Feb | 3O351 | Saiss (FEZ) | Blagnac (TLS) | 13:05 +01 | 15:10 CET | 12:25 +01 | 15:00 CET | |
Disclaimer for 3O351 Flight Radar Data
Flight 3O351 from Saiss to Blagnac 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 3O351 data.
