The Airbus A330 that forced 208 people onto a Maine runway Monday afternoon after smoke filled its business class cabin at 38,000 feet (approximately 11,582 meters) is the same aircraft that evacuated more than 240 passengers onto an Indian runway in April — leaving six people hospitalized and two with broken legs.
That aircraft, tail number HB-JHK, flew back into service on June 4 after extensive repairs following the Delhi engine failure and slide evacuation. It has now been removed from service again while SWISS International Air Lines and the U.S. Federal Aviation Administration investigate an unidentified smoke source that triggered one of aviation’s most feared in-flight emergency responses. The June 4 return to service followed approximately 40 days of inspections and repairs.
The cause of the smoke remains unknown.
What Happened Over the Atlantic on Monday
SWISS Flight LX16 departed Zurich Airport at approximately 10:26 a.m. local time on Monday, July 27 — about 26 minutes behind schedule — for what was scheduled to be an eight-hour transatlantic crossing to New York’s John F. Kennedy International Airport. Flight tracking data confirmed the late pushback from the gate and the aircraft’s subsequent climb to its cruising altitude of between 36,000 and 38,000 feet (approximately 10,973 to 11,582 meters) across the North Atlantic.
Around six and a half hours into the flight, smoke appeared in the forward section of the business class cabin near the coast of Nova Scotia. The flight crew had already initiated a descent to 32,000 feet (approximately 9,754 meters) when, shortly after crossing off the coast of Maine, they squawked the internationally recognized emergency code 7700 — the transponder signal that alerts every radar station monitoring the flight and grants the aircraft immediate priority in the airspace — and requested diversion to Bangor International Airport in Maine.
Flight tracking data showed the aircraft dropping more than 22,000 feet (approximately 6,706 meters) in roughly 10 minutes after the emergency was declared — an aggressive descent consistent with the standard emergency procedure for smoke events, which require flight crews to get the aircraft on the ground as quickly as possible. Aviation A2Z, which tracked the flight in real time, confirmed the rapid descent.
On the Ground: Fire Crews Cleared Thermal Scan
Multiple Bangor Fire Department engines, rescue units, and ambulances were positioned along the runway as LX16 completed its approach. The aircraft touched down safely at approximately 12:14 p.m. ET and came to a full stop on the runway — standard procedure before airport rescue and firefighting teams conducted visual and thermal imaging inspections of the aircraft’s exterior and wheel wells. Simple Flying confirmed the landing time and emergency response deployment.
Those thermal scans found no evidence of fire or heat anywhere on the aircraft. With no fire confirmed, there was no need to evacuate passengers using emergency slides — the method that caused injuries at Delhi in April. After remaining on the runway for nearly an hour during safety checks, the aircraft was cleared to taxi to the terminal. Passengers deplaned normally. Aviation A2Z reported the full sequence of ground inspection and passenger disembarkation.
All 208 passengers and crew were safe, airline spokesperson Michael Pelzer confirmed.
Bangor’s runway reopened at around 12:30 p.m. ET, approximately 30 minutes after the landing, airport spokesperson Aimee Thibodeau confirmed.
Cockpit Fire or Cabin Smoke — A Discrepancy Investigators Have Not Resolved
SWISS described the emergency as “smoke of as yet unknown origin in the forward section of Business Class.” Passengers who described the situation reported noticing an electrical smell, with at least one suggesting it may have originated from a seat.
The FAA’s initial account differed materially. FAA spokesperson Steve Kulm told the Portland Press Herald in an email that the crew had reported a cockpit fire — a categorically different location and severity from the airline’s cabin smoke description — though Kulm noted that information was preliminary and subject to change. The Portland Press Herald’s reporting documented both accounts.
That discrepancy — cockpit fire versus cabin smoke — has not been publicly reconciled. The airline said it would not speculate on the cause until a thorough inspection was complete.
Why Cabin Smoke Commands Immediate Emergency Protocols
Aviation safety protocols treat any unidentified airborne smoke as a potential in-flight fire until thermal inspection or other evidence definitively rules it out. The reason is structural: smoke from a hidden fire in an inaccessible area of the aircraft — inside a wall panel, behind a ceiling section, in a cargo compartment — can build to catastrophic levels before becoming visible, and once it does, time is extremely short.
As aviation safety guidance published by SKYbrary — the ICAO and EUROCONTROL safety knowledge base — states, a significant fire in the passenger cabin is among the worst situations a flight crew can face, with effects including crew incapacitation from toxic fumes and potential loss of aircraft control.
The situation on LX16 carried an additional dimension that would have been visible to the crew: had the smoke developed further into the oceanic portion of the crossing, before the aircraft reached Nova Scotia, the nearest terrain would have been hundreds of miles away. In that scenario, crews of widebody jets crossing the Atlantic must weigh the possibility of an open-ocean emergency landing — a water ditching — as a contingency. The proximity to Nova Scotia when the emergency developed, and the speed with which the crew diverted, reflected exactly this calculus, according to aviation safety analysts.
Is Bangor a Common Emergency Landing Airport for Transatlantic Flights?
Bangor International Airport in Maine sits at a specific geographic advantage that makes it the default diversion point for a large fraction of westbound transatlantic flights. The airport lies directly under the Great Circle Route — the mathematically optimal curved path between North America and Europe — which means it is the first significant American airport encountered by flights approaching from the east. Simple Flying’s analysis of diversion hotspots identifies Bangor’s position as its primary strategic advantage.
The airport’s runway measures more than 10,400 feet (approximately 3,170 meters), long enough to handle any widebody aircraft currently in commercial service. Its airspace is uncongested compared to Boston or New York, and its U.S. Customs and Border Protection facilities allow airlines to process passengers for entry even at an unscheduled stop. A dedicated analysis of Bangor’s diversion role by Simple Flying documents the airport’s long-standing readiness for these events.
Airport records show that between 2004 and 2012, Bangor handled 647 unscheduled landings: 388 for fuel, 139 for weather, 50 for medical reasons, 49 for maintenance issues, and 21 for security reasons. Its reputation traces to its World War II-era construction as a military base for heavy aircraft, which gave it a runway length that remains competitive with any major hub.
What HB-JHK Has Been Through in 2026
The aircraft at the center of Monday’s incident carries a specific history that investigators will now examine against the new event.
On April 26, SWISS flight LX147, operating the Delhi-to-Zurich route with HB-JHK carrying 228 passengers and 4 infants alongside 13 crew members, rejected its takeoff from runway 28 at Indira Gandhi International Airport after the left-hand Rolls-Royce Trent 772B-60 engine experienced a failure and fire alert shortly after 1:00 a.m. local time. The SWISS newsroom confirmed the engine failure and evacuation decision. The aircraft was traveling at approximately 105 knots when the crew aborted — well within the standard abort window, but fast enough that the emergency braking generated intense heat in the main gear wheels and brakes, producing visible smoke and triggering a fire risk.
With fire risks around the landing gear mounting, the crew ordered a full emergency evacuation using inflatable slides. Of the approximately 245 persons on board, six passengers were hospitalized — two of them with broken leg fractures, consistent with the known injury risk of high-speed slide evacuations. AeroInside’s investigation records confirmed the injury count and Indian aviation investigators from the Directorate General of Civil Aviation opened a formal investigation.
Following extensive repairs and inspections, HB-JHK was cleared to return to commercial service on June 4 — approximately 40 days after the Delhi incident.
HB-JHK is an Airbus A330-343X, serial number 1276, nicknamed Herisau after a Swiss municipality, and was delivered to SWISS in January 2012 — making it approximately 14.6 years old at the time of the Bangor incident. Aircraft data from ch-aviation, as published by Simple Flying, confirms these specifications.
What Investigators Will Now Examine
Both SWISS and the FAA have opened investigations into the smoke event on LX16. No timeline for findings has been announced.
The most significant open question — which investigators are likely examining now — is whether the two 2026 incidents on HB-JHK are connected. The Delhi event involved the left Rolls-Royce Trent engine failing under load, generating brake fires, and requiring a full slide evacuation. The Bangor event involved smoke of unidentified origin in the forward business class cabin, with a disputed initial report of a cockpit fire.
Whether the maintenance work performed during HB-JHK’s 40-day ground period after Delhi fully resolved all issues with the aircraft, and whether any finding in the Delhi investigation should have flagged additional inspections of cabin or cockpit electrical systems, are questions that the ongoing investigations will need to address — and questions SWISS has not publicly answered.
What is certain is that the same aircraft has now generated two serious emergency responses in fewer than three months, with six passengers injured in one and 208 aboard when the second occurred. The investigation’s scope and the aircraft’s maintenance record are now under federal scrutiny on two continents.
SWISS also said it was coordinating with Bangor International Airport to arrange alternative travel for all affected LX16 passengers.
What Happened at Portland Jetport Two Days Earlier
Monday’s Bangor diversion was the second aviation emergency in Maine within 72 hours. On Saturday, July 26, Delta Air Lines flight 5860 from Portland International Jetport to New York City declared an emergency and returned to the jetport a few minutes after takeoff when a smoke detector activated due to an electrical issue. Portland fire crews found no smoke on that aircraft; the sensor was believed to be faulty or the result of a circuit board issue. Passengers were accommodated on a replacement aircraft the same day.
The two incidents were unrelated and involved different carriers and aircraft. The coincidence briefly put Maine’s aviation infrastructure in the spotlight.
Frequently Asked QuestionsWhat caused the smoke on the SWISS flight that landed in Bangor?
The cause has not been identified as of the time of publication. SWISS confirmed that smoke of unknown origin appeared in the forward section of business class during the transatlantic crossing, but the airline declined to speculate before completing a thorough technical inspection. The FAA’s initial account — that the crew had reported a cockpit fire — differed from the airline’s cabin smoke description, and that discrepancy has not been publicly resolved. Both the airline and the FAA have open investigations underway.
Is it safe to fly through Bangor, and why do so many flights divert there?
Bangor is not a transit airport — it is a full-service emergency diversion point. Flights are not “flying through” Bangor so much as using it as an emergency landing facility. The airport sits directly on the Great Circle Route, the optimal transatlantic flight path, making it the first major U.S. airport accessible to flights arriving from Europe. Its runway exceeds 10,400 feet (approximately 3,170 meters), it has uncongested airspace, and it maintains U.S. Customs facilities capable of processing international arrivals on short notice. Between 2004 and 2012, it handled 647 unscheduled landings. It is specifically designed and staffed for this role.
Should travelers be concerned that the same aircraft was involved in two serious incidents in 2026?
An aircraft with two documented emergency events in fewer than three months — one involving an engine failure with six injuries, and a second involving unidentified cabin smoke — warrants scrutiny of its maintenance history and investigation findings. The key unanswered question is whether the inspections performed after the Delhi event fully resolved any root cause issues with HB-JHK before the aircraft returned to service, and whether the Delhi investigation’s findings are relevant to the Bangor smoke event. Until investigators answer those questions, travelers cannot assess whether the two incidents are related. Regulators on two continents are now examining both events.
What does squawk 7700 mean and why is it significant?
Squawk 7700 is the internationally standardized transponder code a flight crew broadcasts to signal a general emergency to all air traffic control facilities monitoring the aircraft. Once a flight squawks 7700, it is granted immediate landing priority, other aircraft are cleared from its path, and emergency services at the receiving airport are automatically placed on standby. On LX16, the crew squawked 7700 shortly after crossing the coast of Maine, which is why Bangor’s fire department, rescue units, and ambulances were already positioned on the runway before the aircraft landed.