Bomb Threats Disrupt European Flights as Searches Find No Explosives

Aircraft searches, diversions and an airport closure disrupted European travel on 3 November. Authorities found no explosives on the affected flights, while responsibility remained unconfirmed.

An airport runway extending towards the horizon beneath a cloudy sky. — An airport runway. Contextual photograph; not a scene from the security incidents reported on 3 November. Photograph: Jens Darup / Unsplash.

Bomb threats disrupted at least seven passenger flights across Europe on Tuesday, 3 November, prompting searches, diversions and a temporary airport closure. No explosive devices were found on the affected flights, according to Reuters’ report. Responsibility for the threats had not been established.

The accounts from individual airports show why the disruption cannot be described simply as a series of emergency landings. Some aircraft reached their intended destinations and were inspected there. Others diverted, while restrictions on the ground affected additional services. The common outcome was a completed safety check; the operational consequences differed from airport to airport.

Warsaw’s two airports face separate alerts

A LOT aircraft travelling from London Heathrow to Warsaw Chopin was diverted to Modlin, the Polish capital’s other airport. Reporting by Polish news agency PAP, carried by Radio Kielce, cited the airport’s account: the alert was raised at 9:54 a.m. and the Boeing 737 MAX landed at 10:01 a.m., with 181 people aboard. Modlin suspended operations while the aircraft and the reported threat were assessed.

The airport’s final incident notice said the alarm was cancelled at 12:21 p.m. and normal operations resumed. The effects reached beyond the diverted aircraft: an Edinburgh service scheduled to arrive at 11:30 a.m. landed at 12:49 p.m. after an intermediate stop in Poznań. A Tenerife departure scheduled for 11:45 a.m. left at 12:37 p.m. Those timings document the delays even though the search did not establish an explosive threat.

A separate SAS flight from Copenhagen landed at Chopin and underwent checks. The Associated Press reported that one runway closed during the response. An SAS spokesperson said the aircraft landed normally, rather than making an emergency landing, and that the matter was referred to Polish police.

A military escort into Rome

In Italy, the response included two Eurofighter aircraft launched from Grosseto to intercept and escort a civilian flight from Dublin to Rome Fiumicino. ANSA reported the Italian Air Force’s statement that the passenger aircraft landed safely. The deployment was a response to a reported threat; it did not mean that an explosive device had been confirmed aboard.

Two Ryanair arrivals, from Lisbon and Dublin, were checked at Fiumicino. Sky TG24’s account of the Rome incidents said the inspections covered the aircraft, passengers and baggage after an anonymous report. Police checks concluded shortly after midday without finding explosives. The two arrivals were separate incidents at the same airport, a distinction that matters when counting affected flights and understanding the scale of the response.

Murcia activates a wider emergency response

A Ryanair service from Manchester triggered security procedures at Murcia’s international airport in southeastern Spain. Europa Press reported, citing the airport operator and the regional government delegation, that the flight landed within its scheduled arrival window and that 114 passengers and seven crew members disembarked for checks. National Police, Guardia Civil bomb-disposal specialists, firefighters and medical personnel were involved, and a crisis committee was established at the airport.

Officials subsequently ruled out explosives and airport operations resumed, according to Reuters’ account of the individual incidents. The sequence illustrates the distinction between receiving an alarming message and confirming a physical danger: passengers still had to leave the aircraft and specialists still had to inspect it before normal activity could continue.

Sofia follows a diversion the previous day

Bulgarian Transport Minister Georgi Peev said Tuesday’s threats concerned flights to Sofia from Bergamo and Dublin. Both aircraft were searched and nothing suspicious was found, Bulgarian National Radio reported. Interior Ministry Secretary General Lyubomir Nikolov said the threats arrived by email. The updated account identifies the two European departure cities, clarifying the routes affected as authorities assembled their information.

The previous day, a Wizz Air flight from London Luton to Sofia had diverted to Budapest after an in-flight bomb threat. Radio Bulgaria’s report described the diversion and Hungarian response. Subsequent checks allowed the aircraft to continue to Sofia. Nikolov said on Tuesday that investigators were still trying to identify the sender of the earlier threat, leaving an unresolved inquiry alongside the newly reported alerts.

Responsibility remains an open question

Aviation security specialist Matthew Borie outlined several possible explanations to AP, including copycat behaviour, repeated threats from one person or group, and state-linked activity. These were hypotheses, not an attribution. A shared day of disruption does not, by itself, establish a shared organiser or prove that every message had the same origin.

For the affected airports, the demonstrated consequences were concrete: aircraft had to be isolated or inspected, passengers waited, and some other flights were delayed or rerouted. Establishing whether the threats were coordinated requires evidence about the messages and their senders. The safe resolution of the searches answers the immediate question about the aircraft; it does not yet explain who caused the disruption.