According to AeroTime and Yle, Helsinki-Vantaa International Airport (HEL) suspended all flight operations at approximately 04:00 EEST (01:00 UTC) on 15 May 2026 after Finnish authorities issued a drone-threat alert linked to a Ukrainian overnight strike on Russian territory. An estimated 1.8 million people in the Helsinki metropolitan area received public shelter-in-place guidance. Operations resumed at 07:19 EEST (04:19 UTC); aircraft unable to hold were diverted to Stockholm Arlanda and Rovaniemi. The Kyiv Post reported that Ukraine had pre-warned Finnish authorities before the alert was raised, indicating awareness of a probable incursion risk. No drone crossing into Finnish airspace was confirmed at the time of airport reopening. AirVeto's wind reconstruction at 900 hPa covers the Gulf of Finland and Uusimaa approach corridor during the 04:00 EEST window.
Illustrative file photo. This image is not from the incident described — it shows a military-type UAV of the kind found in field recovery operations.
Helsinki-Vantaa was closed for approximately 3 hours 19 minutes
Helsinki-Vantaa is Finland's primary international hub, handling approximately 23 million passengers per year. The early-morning closure (04:00–07:19 EEST) coincided with the initial wave of Europe-bound long-haul arrivals. Flights unable to hold over the Helsinki TMA were diverted; Stockholm Arlanda and Rovaniemi received the overflow. Finnair confirmed diversions in a customer notice published before 05:00 EEST.
Finnish air-traffic control issued a NOTAM closing the Helsinki TMA. Finavia, the Finnish airport operator, described the closure as a precautionary measure authorised under Finnish law after a credible drone-threat notification. The closure was the first full suspension of HEL operations caused by a drone threat — the March–April 2026 incidents in southeastern Finland had not reached the capital.
Ukraine pre-warned Finland — a procedural evolution from Kouvola
The Kyiv Post's reporting that Ukraine had pre-warned Finnish authorities before the alert was raised marks a notable departure from the March 2026 Kouvola sequence, where Finland received no advance notice. After Kouvola, President Stubb and Prime Minister Orpo both criticised the speed of the public alert; Orpo specifically noted that residents should have been warned more quickly.
The pre-warning on 15 May suggests the information-sharing protocol established after Kouvola — under which Ukraine agreed to alert Finland when a strike package was launched on a heading that put Finnish airspace at risk — was functioning. Finnish authorities appear to have received enough lead time to issue the shelter-in-place guidance and close the airport before any potential crossing.
No crossing into Finnish airspace was confirmed
Despite the closure and the 1.8 million–person shelter-in-place advisory, no drone crossing into Finnish airspace was confirmed at the time Helsinki-Vantaa reopened. Finnish authorities did not announce a drone find in the days following the event. The closure thus differs from the March–April sequence, where physical drone wreckage was recovered: the May 15 event was a precautionary closure based on threat assessment, not a confirmed violation.
This distinction matters for AirVeto's incident classification. The event is logged as a drone alert rather than a confirmed incursion — hence the pin marker rather than explosion. The operational disruption (3+ hours of HEL downtime, 1.8M shelter-in-place) was nonetheless the most significant Finnish aviation event of the spring 2026 sequence.
Wind layer — 900 hPa over the Gulf of Finland on 15 May
AirVeto's wind reconstruction covers the 900 hPa pressure level (approximately 1,000 m) over the Gulf of Finland and the Uusimaa coast during the early morning window of 15 May 2026. The embed above renders the wind field at the time of the alert; methodology is described on the AirVeto methodology page.
Finnish drone incident series — 2026
This event is the fifth in the Finnish airspace incident series. Cross-links to the earlier confirmed violations: