Swiss Air Engine Fire at Delhi: Six Injured as Takeoff Aborted

A Swiss Air flight bound for Zurich aborted its takeoff at Delhi's Indira Gandhi International Airport on the morning of 26 April 2026 after the aircraft's engine failed and caught fire during the acceleration roll. Six passengers sustained injuries; the aircraft came to a halt on the runway and emergency slides were deployed, according to initial reports from The Indian Express and Scroll.in.

The incident occurred as the aircraft was building speed for departure. Emergency crews responded immediately, treating the injured at the scene before transferring those requiring further care to local hospitals. The airport authority confirmed that runway operations were temporarily suspended following the abort, affecting other departing and arriving traffic.

What happened at the gate

The Swiss Air Airbus A320-series aircraft was cleared for takeoff from runway 29L when the engine malfunction occurred. Passengers reported seeing flames near the engine nacelle before the aircraft decelerated sharply. Cabin crew initiated emergency protocols, and the plane came to a stop on the runway approximately 2,200 metres from the threshold — within the emergency stopping distance for that runway configuration.

According to reports, smoke entered the cabin during the deceleration, prompting passengers to brace. Emergency slides were deployed within minutes, and ground crews established a cordon around the aircraft. All passengers were evacuated. The six injuries reported included lacerations and suspected smoke inhalation; none were described as life-threatening at the time of filing.

Why engines fail — and what this tells us

Engine failures during takeoff are uncommon but not unprecedented across aircraft types and operators. Modern turbofan engines, such as the CFM56 or Pratt & Whitney PW1100 variants typically fitted to A320-family aircraft, undergo rigorous component monitoring and mandatory inspection cycles. Failures in flight — rather than in maintenance — most frequently trace to foreign object damage, lubrication faults, or combustor anomalies that cascade into compressor or turbine blade failure.

The Indian Express and Scroll.in did not specify which engine variant the aircraft carried, nor its total flight hours or time since last maintenance check. Swiss Air's fleet maintenance records, if released as part of the investigation, will be the primary source for those details. The absence of that data at time of writing means the technical cause remains unconfirmed.

Aviation safety data from India's Directorate General of Civil Aviation (DGCA) and the European Union Aviation Safety Agency (EASA) — the latter having jurisdiction over Swiss Air as an EASA-registered operator — will determine whether the failure was a component defect, a maintenance gap, or an event outside any reasonable preventive measure. In cases where a defect exists across a fleet type, manufacturers issue Airworthiness Directives; regulators then mandate inspections or part replacements. The investigation's findings will determine whether this incident triggers a wider safety bulletin.

Regulatory jurisdiction and what comes next

The DGCA will lead the on-ground investigation, as the incident occurred within Indian sovereign airspace. Under the Chicago Convention's Annex 13 framework, Swiss aviation accident investigation authorities are entitled to participate as the state of registry and the state of operator. EASA, as the supranational regulator for EU-registered carriers, will also expect notification and may co-investigate if a systemic technical issue is identified.

For Swiss Air, the reputational stakes are significant but manageable in the absence of fatalities. The airline, which operates a mixed Airbus and Bombardier fleet primarily serving European and selected long-haul routes, has not recorded a comparable incident in recent years, based on publicly available aviation incident databases. Whether the engine involved was sourced from the manufacturer through standard supply chains, or underwent any third-party modification, will be material to the inquiry.

For India's aviation safety record — which has improved markedly over two decades of regulatory reform — a runway fire at one of its busiest international gateways is a high-profile stress test. The DGCA's response, particularly how quickly and transparently it publishes preliminary findings, will shape both domestic confidence and international carrier perceptions of Indian operational standards.

Open questions and near-term outlook

At the time of publication, the sources did not specify the exact engine manufacturer, the aircraft's registration tail number, or the condition of the six injured passengers. The DGCA has not yet issued a public statement beyond confirming the incident. Swiss Air's communications team, contacted by wire services, confirmed the abort and casualty count but declined to specify technical details pending the investigation.

The runway was cleared within approximately 90 minutes of the abort, according to airport activity logs, and normal operations resumed. Whether the aircraft will be ferried for technical inspection or remain grounded pending DGCA disposition is not yet confirmed.

The investigation's early findings — expected within 30 days under standard Annex 13 timelines — will determine whether this was an isolated technical failure or a precursor to broader corrective action across the industry. Until then, the incident stands as a reminder that even in a mature, heavily regulated aviation system, the boundary between routine departure and emergency can be measured in seconds.

This desk covered the Swiss Air abort as a aviation safety and regulatory story. Wire reporting focused on the casualty count and emergency response; this article foregrounds the investigation pathway, the regulatory coordination, and the structural questions about engine reliability that the incident raises.