Departure (OR393 Flight Schedule)
Willemstad, Netherlands AntillesAST 00:00:00 DAY
Arrival (OR393 Flight Schedule)
Amsterdam, NetherlandsCET 00:00:00 DAY
Flight Radar Checker UG 393
Live Flight Tracker Map
Flight OR393 from Willemstad to Amsterdam is operated by Tuninter. Scheduled time of departure from Hato is 18:50 AST and scheduled time of arrival in Schiphol is 09:40 CET. The duration of the flight is 9 hours 50 minutes.
Flight Finder
from Amsterdam to Willemstad
History Flight Information for OR393 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Fri, 21 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | PH-TFM (Boeing B788) | 03:15 AST | 09:42 CET |
| Fri, 21 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 21 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | PH-TFM (Boeing B788) | 11:55 CET | 08:12 AST |
| Wed, 19 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | 04:17 AST | 10:41 CET | |
| Wed, 19 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 19 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | 12:40 CET | 09:18 AST | |
| Fri, 14 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | OO-JDL (Boeing B788) | 02:43 AST | 09:01 CET |
| Fri, 14 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 14 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | OO-JDL (Boeing B788) | 11:31 CET | 07:55 AST |
| Wed, 12 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | PH-TFM (Boeing B788) | 04:37 AST | 11:13 CET |
| Wed, 12 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 12 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | PH-TFM (Boeing B788) | 12:44 CET | 09:05 AST |
| Fri, 07 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | PH-TFK (Boeing B788) | 03:16 AST | 09:40 CET |
| Fri, 07 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 07 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | PH-TFK (Boeing B788) | 11:33 CET | 07:51 AST |
| Wed, 05 Feb | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | OO-JDL (Boeing B788) | 03:58 AST | 10:38 CET |
| Wed, 05 Feb | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 05 Feb | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | OO-JDL (Boeing B788) | 12:35 CET | 08:51 AST |
| Fri, 31 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | |||
| Fri, 31 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 31 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | PH-TFK (Boeing B788) | 10:49 CET | 09:24 AST |
| Wed, 29 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | PH-TFM (Boeing B788) | 05:19 AST | 11:38 CET |
| Wed, 29 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 29 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | PH-TFM (Boeing B788) | 12:55 CET | 11:34 AST |
| Fri, 24 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | OO-JDL (Boeing B788) | 02:46 AST | 08:53 CET |
| Fri, 24 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 24 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | OO-JDL (Boeing B788) | 10:56 CET | 09:58 AST |
| Wed, 22 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | PH-TFK (Boeing B788) | 04:18 AST | 10:28 CET |
| Wed, 22 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 22 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | PH-TFK (Boeing B788) | 13:24 CET | 12:00 AST |
| Fri, 17 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | OO-JDL (Boeing B788) | 02:24 AST | 08:59 CET |
| Fri, 17 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 17 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | OO-JDL (Boeing B788) | 10:58 CET | 09:32 AST |
| Wed, 15 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | 03:31 AST | 10:01 CET | |
| Wed, 15 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 15 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | 12:21 CET | 11:09 AST | |
| Fri, 10 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | OO-JDL (Boeing B788) | 02:38 AST | 09:04 CET |
| Fri, 10 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 10 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | OO-JDL (Boeing B788) | 11:23 CET | 07:53 AST |
| Wed, 08 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | PH-TFK (Boeing B788) | 04:03 AST | 10:14 CET |
| Wed, 08 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 08 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | PH-TFK (Boeing B788) | 12:29 CET | 11:18 AST |
| Fri, 03 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 18:50 AST | 09:40 CET | OO-JDL (Boeing B788) | 03:07 AST | 09:24 CET |
| Fri, 03 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 16:40 AST | 17:50 AST | |||
| Fri, 03 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 10:30 CET | 16:10 AST | OO-JDL (Boeing B788) | 11:29 CET | 08:11 AST |
| Wed, 01 Jan | OR393 | Hato (CUR) | Schiphol (AMS) | 20:35 AST | 11:25 CET | PH-TFM (Boeing B788) | 04:16 AST | 10:43 CET |
| Wed, 01 Jan | OR393 | Flamingo (BON) | Hato (CUR) | 18:25 AST | 19:35 AST | |||
| Wed, 01 Jan | OR393 | Schiphol (AMS) | Flamingo (BON) | 12:15 CET | 17:55 AST | PH-TFM (Boeing B788) | 12:31 CET | 16:32 AST |
Disclaimer for OR393 Flight Radar Data
Flight OR393 from Hato to Schiphol 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 OR393 data.
