Vols
Date | Vol | Origine | STD | Destination | STA | Avion | Statut | Durée | Repasser |
---|---|---|---|---|---|---|---|---|---|
2024 3 mai | Tromsø (TOS/ENTC) | BE20 (LN-BSJ) | Departed | ||||||
2024 3 mai | Trondheim (TRD/ENVA) | BE20 (LN-BSD) | Departed | ||||||
2024 2 mai | First seen near Sørkjosen, Norway | Tromsø (TOS/ENTC) | BE20 (LN-BSJ) | Landed 00:02 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | First seen near Årø, Norway | Trondheim (TRD/ENVA) | BE20 (LN-BSD) | Landed 23:23 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | Mo i Rana (MQN/ENRA) | BE20 (LN-BSG) | Departed | ||||||
2024 2 mai | Evenes (EVE/ENEV) | Tromsø (TOS/ENTC) | BE20 (LN-BSB) | Landed 22:58 CEST Landing time derived from ADS-B/Radar data | 00h23m | ||||
2024 2 mai | First seen near Årø, Norway | BE20 (LN-BSD) | Status N/A | ||||||
2024 2 mai | Bodø (BOO/ENBO) | BE20 (LN-BSG) | Departed | ||||||
2024 2 mai | Tromsø (TOS/ENTC) | Evenes (EVE/ENEV) | BE20 (LN-BSB) | Landed 21:40 CEST Landing time derived from ADS-B/Radar data | 00h26m | ||||
2024 2 mai | Hadsel (SKN/ENSK) | Bodø (BOO/ENBO) | BE20 (LN-BSG) | Landed 20:32 CEST Landing time derived from ADS-B/Radar data | 00h21m | ||||
2024 2 mai | Tromsø (TOS/ENTC) | BE20 (LN-BSC) | Departed | ||||||
2024 2 mai | Bodø (BOO/ENBO) | Hadsel (SKN/ENSK) | BE20 (LN-BSG) | Landed 19:48 CEST Landing time derived from ADS-B/Radar data | 00h27m | ||||
2024 2 mai | First seen near Sørkjosen, Norway | Tromsø (TOS/ENTC) | BE20 (LN-BSC) | Landed 19:04 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | Tromsø (TOS/ENTC) | Tromsø (TOS/ENTC) | BE20 (LN-BSB) | Landed 20:06 CEST Landing time derived from ADS-B/Radar data | 01h24m | ||||
2024 2 mai | Bodø (BOO/ENBO) | BE20 (LN-BSJ) | Departed | ||||||
2024 2 mai | Hadsel (SKN/ENSK) | Bodø (BOO/ENBO) | BE20 (LN-BSJ) | Landed 16:59 CEST Landing time derived from ADS-B/Radar data | 00h23m | ||||
2024 2 mai | Tromsø (TOS/ENTC) | Hadsel (SKN/ENSK) | BE20 (LN-BSJ) | Landed 16:13 CEST Landing time derived from ADS-B/Radar data | 00h38m | ||||
2024 2 mai | Alstahaug (SSJ/ENST) | Tromsø (TOS/ENTC) | BE20 (LN-BSB) | Landed 16:14 CEST Landing time derived from ADS-B/Radar data | 01h16m | ||||
2024 2 mai | First seen near Hasvik, Norway | Tromsø (TOS/ENTC) | BE20 (LN-BSJ) | Landed 15:10 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | First seen near Mo i Rana, Norway | BE20 (LN-BSB) | Status N/A | ||||||
2024 2 mai | Bergen (BGO/ENBR) | 14:10 CEST | Oslo (OSL/ENGM) | 14:46 CEST | C68A (LN-SAA) | Landed 14:45 CEST Landing time derived from ADS-B/Radar data | 00h36m | ||
2024 2 mai | Stavanger (SVG/ENZV) | 11:45 CEST | Bergen (BGO/ENBR) | 13:39 CEST | C68A (LN-SAA) | Landed 13:38 CEST Landing time derived from ADS-B/Radar data | 00h18m | ||
2024 2 mai | Bergen (BGO/ENBR) | Stavanger (SVG/ENZV) | C68A (LN-SAA) | Landed 12:22 CEST Landing time derived from ADS-B/Radar data | 00h23m | ||||
2024 2 mai | Tromsø (TOS/ENTC) | Mo i Rana (MQN/ENRA) | BE20 (LN-BSB) | Landed 13:40 CEST Landing time derived from ADS-B/Radar data | 00h59m | ||||
2024 2 mai | Trondheim (TRD/ENVA) | BE20 (LN-BSD) | Departed | ||||||
2024 2 mai | Tromsø (TOS/ENTC) | BE20 (LN-BSJ) | Departed | ||||||
2024 2 mai | Oslo (OSL/ENGM) | 10:00 CEST | Bergen (BGO/ENBR) | 10:31 CEST | C68A (LN-SAA) | Landed 10:30 CEST Landing time derived from ADS-B/Radar data | 00h34m | ||
2024 2 mai | First seen near Sørkjosen, Norway | Tromsø (TOS/ENTC) | BE20 (LN-BSJ) | Landed 09:54 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | First seen near Ålesund, Norway | Trondheim (TRD/ENVA) | BE20 (LN-BSD) | Landed 10:00 CEST Landing time derived from ADS-B/Radar data | |||||
2024 2 mai | Tromsø (TOS/ENTC) | Bodø (BOO/ENBO) | BE20 (LN-BSG) | Landed 10:08 CEST Landing time derived from ADS-B/Radar data | 00h47m |
L'historique des vols pour Babcock Scandinavian Air Ambulance 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.