| ARRIVED 57 HOUR 20 MINUTES AGO |
 |  |
Departure (3O836 Flight Schedule)
Bilbao, SpainCEST 00:00:00 DAY
Arrival (3O836 Flight Schedule)
Tanger, Morocco+01 00:00:00 DAY
Flight Radar Checker E5 836
Live Flight Tracker Map
Flight 3O836 from Bilbao to Tanger is operated by Air Arabia Maroc. Scheduled time of departure from Bilbao is 14:25 CEST and scheduled time of arrival in Ibn Batouta is 15:05 +01. The duration of the flight is 1 hour 40 minutes.
Not Rated
History Flight Information for 3O836 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Mon, 01 Sep | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 14:32 CEST | 14:44 +01 | |
| Fri, 29 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | CN-NML ( A320) | 14:34 CEST | 14:47 +01 |
| Mon, 25 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 14:35 CEST | 14:48 +01 | |
| Fri, 22 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 15:04 CEST | 15:18 +01 | |
| Mon, 18 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 15:00 CEST | 15:21 +01 | |
| Fri, 15 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | CN-NMJ (Airbus A320) | 15:09 CEST | 15:15 +01 |
| Mon, 11 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | CN-NMJ (Airbus A320) | 15:26 CEST | 14:57 +01 |
| Fri, 08 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 14:49 CEST | 15:05 +01 | |
| Mon, 04 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | CN-NMH (Airbus A320) | 14:49 CEST | 14:56 +01 |
| Fri, 01 Aug | 3O836 | Bilbao (BIO) | Ibn Batouta (TNG) | 14:25 CEST | 15:05 +01 | 14:47 CEST | 14:57 +01 | |
Disclaimer for 3O836 Flight Radar Data
Flight 3O836 from Bilbao to Ibn Batouta 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 3O836 data.
