Vols
Date | Vol | Origine | STD | Destination | STA | Avion | Statut | Durée | Repasser |
---|---|---|---|---|---|---|---|---|---|
2024 4 mai | Mirny (MJZ/UERR) | 18:00 YAKT | Novosibirsk (OVB/UNNT) | 19:05 NOVT | B738 | Scheduled | 03h05m | ||
2024 4 mai | Moscow (VKO/UUWW) | 11:00 MSK | St. Petersburg (LED/ULLI) | 12:40 MSK | B738 | Scheduled | 01h40m | ||
2024 4 mai | Mirny (MJZ/UERR) | 16:30 YAKT | Yakutsk (YKS/UEEE) | 18:45 YAKT | AN24 | Scheduled | 02h15m | ||
2024 4 mai | Yakutsk (YKS/UEEE) | 13:00 YAKT | Mirny (MJZ/UERR) | 15:15 YAKT | AN24 | Scheduled | 02h15m | ||
2024 4 mai | Lensk (ULK/UERL) | 12:50 YAKT | Mirny (MJZ/UERR) | 13:40 YAKT | AN24 | Scheduled | 00h50m | ||
2024 4 mai | Irkutsk (IKT/UIII) | 11:45 IRKT | Mirny (MJZ/UERR) | 14:35 YAKT | B738 | Scheduled | 01h50m | ||
2024 4 mai | Mirny (MJZ/UERR) | 10:30 YAKT | Lensk (ULK/UERL) | 11:20 YAKT | AN24 | Scheduled | 00h50m | ||
2024 4 mai | Mirny (MJZ/UERR) | 10:00 YAKT | Moscow (VKO/UUWW) | 10:05 MSK | B738 | Scheduled | 06h05m | ||
2024 4 mai | Mirny (MJZ/UERR) | 09:30 YAKT | Irkutsk (IKT/UIII) | 10:20 IRKT | B738 | Scheduled | 01h50m | ||
2024 4 mai | Novosibirsk (OVB/UNNT) | 02:15 NOVT | Mirny (MJZ/UERR) | 07:00 YAKT | B738 | Scheduled | 02h45m | ||
2024 3 mai | Moscow (VKO/UUWW) | 20:20 MSK | Mirny (MJZ/UERR) | 08:00 YAKT | B738 | Scheduled | 05h40m | ||
2024 3 mai | Moscow (VKO/UUWW) | 15:45 MSK | Novosibirsk (OVB/UNNT) | 23:45 NOVT | B738 | Scheduled | 04h00m | ||
2024 3 mai | Chicago, IL (ORD/KORD) | 05:02 CDT | Mexico (NLU/MMSM) | 07:58 CST | B762 | Estimated | 03h43m | ||
2024 3 mai | Novosibirsk (OVB/UNNT) | 13:15 NOVT | Moscow (VKO/UUWW) | 13:35 MSK | B738 | Scheduled | 04h20m | ||
2024 3 mai | New York, NY (JFK/KJFK) | 01:38 EDT | Chicago, IL (ORD/KORD) | 03:22 CDT | B762 | Estimated | 02h31m | ||
2024 3 mai | Yakutsk (YKS/UEEE) | 11:40 YAKT | Mirny (MJZ/UERR) | 13:55 YAKT | AN24 | Scheduled | 02h15m | ||
2024 3 mai | First seen near El Segundo, CA, United States | A306 (XA-UYR) | Status N/A | ||||||
2024 3 mai | Mirny (MJZ/UERR) | 08:20 YAKT | Yakutsk (YKS/UEEE) | 10:40 YAKT | AN24 | Scheduled | 02h20m | ||
2024 2 mai | Guatemala City (GUA/MGGT) | 16:43 CST | New York, NY (JFK/KJFK) | B762 (XA-LRC) | Landed 22:35 EDT Landing time derived from ADS-B/Radar data | 04h28m | |||
2024 2 mai | Miami, FL (MIA/KMIA) | 14:10 EDT | Guatemala City (GUA/MGGT) | B762 (XA-LRC) | Landed 14:13 CST Landing time derived from ADS-B/Radar data | 02h12m | |||
2024 2 mai | Los Angeles, CA (LAX/KLAX) | 10:30 PDT | Monterrey (MTY/MMMY) | A306 | Scheduled | ||||
2024 2 mai | Novosibirsk (OVB/UNNT) | 20:00 NOVT | Moscow (VKO/UUWW) | 20:20 MSK | B737 (RA-73268) | Landed 19:56 MSK Landing time derived from ADS-B/Radar data | 03h56m | ||
2024 2 mai | Mirny (MJZ/UERR) | 10:30 YAKT | Novosibirsk (OVB/UNNT) | 11:25 NOVT | B738 | Scheduled | 02h55m | ||
2024 1 mai | La Mesa (SAP/MHLM) | Miami, FL (MIA/KMIA) | B762 (XA-LRC) | Landed 14:30 EDT Landing time derived from ADS-B/Radar data | 01h54m | ||||
2024 1 mai | Mexico (NLU/MMSM) | 10:18 CST | Bogota (BOG/SKBO) | - | Landed 14:49 COT Landing time derived from company/airport information | ||||
2024 1 mai | Mexico (NLU/MMSM) | Bogota (BOG/SKBO) | A332 (N334QT) | Landed 14:43 COT Landing time derived from ADS-B/Radar data | 03h39m | ||||
2024 1 mai | Guatemala City (GUA/MGGT) | La Mesa (SAP/MHLM) | B762 (XA-LRC) | Landed 09:21 CST Landing time derived from ADS-B/Radar data | |||||
2024 1 mai | Moscow (VKO/UUWW) | 15:45 MSK | Novosibirsk (OVB/UNNT) | 23:45 NOVT | B738 (RA-73264) | Landed | 04h00m | ||
2024 1 mai | Los Angeles, CA (LAX/KLAX) | 04:18 PDT | Mexico (NLU/MMSM) | A332 (N334QT) | Landed 08:13 CST Landing time derived from ADS-B/Radar data | 02h53m | |||
2024 1 mai | Mérida (MID/MMMD) | 04:15 CST | Los Angeles, CA (LAX/KLAX) | A306 (XA-UYR) | Landed 10:56 PDT Landing time derived from ADS-B/Radar data | 04h33m |
L'historique des vols pour AeroUnion est disponible pour une période de plus de 7 jours sous notre Basique abonnement. Plus de détails ici
Plus de données d'aéroport sont disponibles à l'achat. Veuillez consulter notre API à la demande.