Wizz Air Flight Diversion to Budapest After Bomb Threat Disrupts London–Sofia Route as NATO Scrambles Gripen Jet

A Wizz Air flight from London Luton to Sofia diverted to Budapest on November 2, 2026, after the crew received a bomb threat mid-flight, triggering an emergency security response across Hungarian airspace. The Airbus A321neo, operating as flight W64302, landed safely at Budapest Ferenc Liszt International Airport at 12:08 pm local time. The incident prompted a NATO ALPHA alert, sending a Hungarian Gripen fighter jet to escort the passenger aircraft. Hungarian police, firefighters and counter-terrorism personnel subsequently attended the aircraft for security inspections. Budapest Airport also temporarily closed one runway while emergency teams managed the situation, although other flight operations continued. The incident disrupted the London–Sofia journey and highlighted Europe’s coordinated response to potential threats involving commercial passenger aircraft.

Wizz Air Diverts From Its London–Sofia Route

The incident involved Wizz Air flight W64302, which operated between London Luton and Sofia on 2 November. The Airbus A321neo departed London at approximately 08:33 GMT. It was scheduled to reach Sofia at around 13:25 local time.

However, a reported bomb threat interrupted the journey while the aircraft was flying over Bosnia and Herzegovina. The crew changed course and requested permission to land at Budapest Ferenc Liszt International Airport in Hungary.

The diversion brought the aircraft into Hungarian airspace under heightened security arrangements. Hungary’s air-defence readiness service subsequently issued a NATO ALPHA alert. Hungarian Gripen fighter aircraft took off to escort the passenger jet towards Budapest.

The aircraft landed safely at approximately 12:08 pm local time. It then taxied to a designated parking position, where emergency services and security personnel were waiting. The incident immediately shifted attention from the aircraft’s diversion to the wider security response at one of Central Europe’s important aviation gateways.

The development also affected passengers travelling beyond Budapest. Those booked on the London–Sofia service faced an unexpected interruption, while passengers using Budapest Airport encountered temporary changes to runway operations.

Hungarian Gripen Responds to NATO ALPHA Alert

The military response became one of the defining features of the incident. Hungary’s defence authorities confirmed that the NATO air-defence readiness service issued an ALPHA alert following the reported threat.

A Hungarian Saab JAS 39 Gripen fighter jet was scrambled within minutes. Its assignment involved escorting the passenger aircraft and supporting its safe approach to Budapest.

Hungarian Defence Minister Romulusz Ruszin-Szendi confirmed the deployment. He praised the speed of the military response and highlighted the readiness of personnel responsible for protecting Hungarian airspace.

The Gripen returned to its base at Kecskemét after completing the escort mission. Meanwhile, Hungarian police assumed responsibility for the security response following the aircraft’s arrival.

The ALPHA alert should not be confused with confirmation of an attack or an actual explosive device. It represents an alert within the air-defence readiness response described by Hungarian authorities. The military escort formed part of the wider precautionary measures surrounding the threatened passenger aircraft.

The incident demonstrates how civilian aviation and national air-defence systems can coordinate during an unusual security event. It also highlights the importance of rapid communication between flight crews, air traffic control, military personnel and airport emergency services.

Security Teams Inspect Aircraft and Passengers

The aircraft’s safe landing marked the beginning of a comprehensive ground security operation. Budapest Airport emergency services had positioned personnel near the designated parking stand.

Firefighters, police officers and counter-terrorism personnel attended the aircraft. Authorities began inspecting the aircraft and passengers under established security procedures.

Wizz Air confirmed that it was cooperating with the relevant authorities. The airline also reiterated its commitment to passenger and crew safety.

However, subsequent reporting brought an important update. Sky News reported on 2 November that the aircraft inspection found nothing. Wizz Air subsequently expected the aircraft to resume its journey to Sofia.

This development is significant for passengers because it distinguishes the initial security warning from the eventual inspection findings. A reported threat does not necessarily indicate that an explosive device exists.

Authorities had not publicly established the origin of the threat in the available reporting. Nor had they disclosed who might have been responsible. Therefore, the incident should remain described as a bomb-threat response rather than a confirmed attempted attack.

The distinction matters for aviation reporting. It avoids presenting an unverified security allegation as an established criminal incident.

Budapest Airport Manages Temporary Runway Disruption

The security operation also affected airport infrastructure. Reports indicated that Budapest Airport temporarily closed one runway while emergency teams managed the aircraft.

The airport continued handling arriving and departing flights through its remaining operational runway. Consequently, the incident did not amount to a complete airport shutdown.

This distinction is particularly important for international travellers. Budapest serves as a connecting point for passengers moving between Western, Central and Eastern Europe. Even a temporary runway restriction can require air traffic controllers to adjust arrival sequences and departure arrangements.

Budapest Airport operates a two-runway system. Its published aeronautical information describes procedures for single-runway operations. These arrangements allow aircraft movements to continue when one runway becomes unavailable, subject to operational and safety requirements.

The temporary restriction therefore illustrates the importance of airport contingency planning. Nevertheless, the exact number of flights delayed or affected by this particular incident has not been established.

For travellers with onward connections, the most important consideration remains the actual flight status. A runway restriction does not automatically mean that every flight experiences a delay.

Passengers should also distinguish between an airport-wide operational disruption and an isolated aircraft security response. The two situations carry different implications for connecting itineraries and airline assistance.

What Happened to Passengers Travelling to Sofia?

The diversion interrupted the original London–Sofia itinerary. Instead of proceeding directly to Bulgaria, the aircraft landed in Hungary for security checks.

However, the subsequent inspection produced a reassuring operational update. Wizz Air confirmed that nothing had been found, and the aircraft was expected to continue towards Sofia.

For passengers, the immediate concern was not simply the diversion itself. They also needed clarity about onward travel, arrival times, baggage arrangements and possible missed connections.

A diversion can create several practical complications, even when an aircraft lands safely. Passengers with connecting flights may lose their original connections. Those arranging airport transfers, accommodation or business appointments may also face unexpected costs.

In this case, the reported intention to resume the Sofia journey reduced the likelihood of passengers needing a completely separate replacement service. Nevertheless, individual arrival times and subsequent arrangements would determine the actual disruption.

Wizz Air’s communication with passengers would therefore remain important. Travellers should retain boarding passes, booking confirmations and receipts for reasonable additional expenses.

The incident also reinforces the importance of providing airlines with accurate contact information. Operational updates can change quickly during security incidents, particularly when authorities control access to the aircraft.

European Passenger Rights During Security Diversions

The incident raises an important question about passenger compensation. European aviation regulations provide specific protections when flights experience cancellations, significant delays or changes to their destinations.

Under EU Regulation 261/2004, passengers may qualify for assistance, reimbursement, rerouting or compensation, depending on the circumstances.

However, security risks can constitute extraordinary circumstances. Airlines may avoid paying standard financial compensation when they demonstrate that an extraordinary event caused the disruption. They must also show that reasonable measures could not have prevented the resulting cancellation or delay.

This does not automatically remove every passenger entitlement. The right to assistance and applicable rerouting arrangements can remain relevant, depending on the circumstances.

An important distinction applies to this particular incident. A diversion does not automatically constitute a cancellation under European passenger-rights rules.

If passengers reach their original destination through an alternative arrangement, the legal classification depends on the circumstances. Arrival at a different airport can also have different consequences under EU rules.

Passengers should therefore check their actual arrival time at Sofia rather than relying solely on the scheduled landing time.

The European Commission’s passenger-rights guidance explains these distinctions. Wizz Air also publishes information about assistance, delays and compensation claims.

How Security Threats Affect Airline Operations

Bomb threats involving passenger aircraft create operational consequences extending beyond the affected flight. Airlines must coordinate with air traffic control, airport operators, police and national security authorities.

The initial response usually prioritises the safety of passengers and crew. Flight crews follow established procedures and communicate with the relevant authorities. Depending on the threat assessment, controllers may coordinate a diversion to an airport capable of handling the emergency.

The airport then prepares the necessary emergency response. Security personnel assess the aircraft, passengers and surrounding operational area. Meanwhile, airport authorities may restrict access or temporarily adjust runway availability.

These measures can affect other airlines using the same airport. However, the scale depends on the duration of restrictions and the availability of alternative operational facilities.

The Budapest incident demonstrates this interconnected operational structure. A threat received aboard one aircraft required coordination between the airline, Hungarian military personnel, airport authorities and police.

It also highlights why airlines cannot treat security-related diversions as ordinary schedule changes. Their immediate priority must remain the safe handling of the aircraft and the people aboard.

Earlier European Incidents Highlight Aviation Risks

The Budapest diversion came amid other reported aviation security incidents across Europe. These events illustrate how different emergency situations can trigger military escorts, airport restrictions and precautionary diversions.

One relevant example occurred on 18 October 2026. An Austrian Airlines flight travelling from Tel Aviv to Vienna reportedly diverted to Sofia following a bomb threat.

A Bulgarian Air Force MiG-29 escorted that aircraft. Subsequent inspections reportedly found no explosive device, allowing the flight to resume its journey.

The two incidents involved different airlines, countries and military aircraft. Nevertheless, both demonstrated how European authorities can coordinate civilian aviation responses with national air-defence capabilities.

These comparisons should not suggest that every bomb threat produces an identical response. Authorities assess each incident according to its circumstances, location and available information.

The broader lesson concerns preparedness. Airlines and airports must maintain procedures capable of accommodating unexpected security events without unnecessarily suspending wider operations.

What Travellers Should Check Before Departure

Passengers travelling through Budapest, London Luton or Sofia should monitor their airline’s operational updates following security-related disruptions.

For Wizz Air passengers, the airline’s official website and mobile application provide booking information and flight-status updates. Travellers should check their departure terminal, boarding time and any revised arrival arrangements before leaving for the airport.

Passengers with onward connections should contact their airlines if the disruption affects separate bookings. They should also confirm whether their original connection remains valid.

Budapest-bound travellers should not assume that a temporary runway closure means all airport services have stopped. Instead, they should follow airport announcements and check their individual flight status.

For passengers affected by similar incidents, retaining receipts and travel documentation can help support subsequent assistance or reimbursement requests.

Aviation Security Remains a Priority for Europe

The Wizz Air incident highlights the importance of coordinated aviation security across European airspace. A reported threat prompted an immediate diversion, a Hungarian military response and precautionary airport restrictions.

The subsequent inspection found no suspicious device, according to Wizz Air’s update reported by Sky News. The aircraft was expected to continue its journey to Sofia. Nevertheless, the investigation into the threat remained a separate matter.

For airlines, airports and travellers, the incident reinforces the importance of preparedness, communication and passenger assistance. Operational continuity must follow security clearance, never precede it. Budapest’s response also demonstrated how an airport can maintain wider operations while handling an isolated emergency.

Essential Flight and Incident Information