Regulations & Safety
SWISS A330 Engine Fire Triggers Emergency Evacuation in Delhi
SWISS flight LX 147 aborted takeoff at Delhi after left engine fire. Six passengers injured during evacuation; runway briefly closed.

SWISS A330 Evacuated in Delhi Following Engine Fire
A SWISS International Air Lines flight bound for Zurich was forced to abort its takeoff and evacuate passengers on the runway at Delhi’s Indira Gandhi International Airport (IGIA) early Sunday morning following an engine fire. According to reporting by the Times of India and journalist Saurabh Sinha, the incident resulted in the hospitalization of six passengers who sustained injuries during the emergency evacuation.
The aircraft, a widebody Airbus A330, experienced a severe failure in its number one engine during the takeoff roll, prompting the flight crew to initiate a high-speed rejected takeoff. As reported by the Times of India, the sudden engine issue and subsequent fire scare led to a full emergency declaration at India’s busiest aviation hub, temporarily halting operations on the affected runway.
Details of the Rejected Takeoff
Flight LX 147 was scheduled to operate a routine long-haul sector from New Delhi to Zurich on Sunday, April 26, 2026. According to the Times of India, the Airbus A330-300, registered as HB-JHK, was accelerating down Runway 28 at approximately 1:08 a.m. local time when the left engine suffered a critical malfunction.
Flight tracking data from Flightradar24, cited in the original reporting by Saurabh Sinha, indicates that the aircraft had reached a speed of 104 knots when the engine failure occurred. The flight crew immediately aborted the takeoff procedure, applying maximum braking and reverse thrust on the operational engine to bring the heavy aircraft to a safe halt on the runway before ordering an emergency evacuation.
The sudden deceleration and the presence of smoke and fire on the left side of the aircraft created a highly stressful environment for the occupants. The Times of India reports that there were 232 passengers on board the flight, including four infants, alongside the operating flight crew.
Emergency Evacuation and Passenger Injuries
With smoke and fire reported near the left engine, the captain ordered an immediate evacuation. The crew deployed the aircraft’s emergency escape slides to facilitate a rapid egress.
During the high-stakes evacuation, several occupants sustained injuries. According to Saurabh Sinha’s reporting, six passengers were transported to Medanta Hospital for medical evaluation and treatment. Injuries during slide evacuations are common, often resulting from the steep angle of descent and passengers colliding at the bottom of the slide.
In a public statement released following the incident and quoted by the Times of India, the airline confirmed the sequence of events and the crew’s decision-making process.
“The crew rejected the takeoff and, following an assessment of the situation, decided as a precaution to evacuate the aircraft,” SWISS stated.
The airline further noted that local teams were immediately deployed to assist stranded passengers. SWISS confirmed that they were working intensively to arrange hotel accommodations and rebooking options for those affected by the aborted flight. Furthermore, the airline announced that technical specialists would be dispatched to Delhi to inspect the damaged Airbus A330 and investigate the root cause of the engine failure.
Airport Response and Operational Impact
The aborted takeoff triggered an immediate and massive response from the airport’s rescue and firefighting services. A full emergency was declared at IGIA, with multiple fire tenders dispatched to Runway 28 to secure the aircraft, extinguish any remaining fire, and assist with the passenger evacuation process.
According to supplementary reporting by The Tribune, the fire department was alerted to a full hydraulic emergency, prompting a rapid deployment of emergency vehicles to the tarmac. The Times of India noted that Runway 28 was temporarily closed to allow emergency crews to manage the scene, treat the injured, and safely tow the disabled Airbus A330 from the active runway area.
Despite the closure of Runway 28, Delhi Airport officials released a statement confirming that overall airport operations remained largely unaffected, with air traffic being routed to the airport’s other available runways.
AirPro News analysis
We note that high-speed rejected takeoffs (RTOs) are among the most critical and demanding maneuvers in commercial aviation. At 104 knots, the SWISS Airbus A330 was traveling at a significant velocity, though we assess it was likely still below V1, the critical decision speed at which a takeoff can no longer be safely aborted. The successful deceleration of the heavy widebody aircraft underscores the rigorous simulator training flight crews undergo for engine-out scenarios during the takeoff roll.
Evacuation injuries, such as the six hospitalizations reported in this incident, are unfortunately a standard risk when deploying emergency slides. The steep angle of widebody aircraft slides, combined with the urgency and panic of a fire-related evacuation, frequently results in minor to moderate injuries. However, we believe the swift and decisive actions of the SWISS flight crew undoubtedly prevented a more severe outcome by ensuring all 232 passengers exited the potentially compromised airframe within the mandated 90-second safety margin.
Furthermore, the dispatch of SWISS technical specialists to Delhi highlights the seriousness of uncontained or fire-producing engine failures. We expect investigators will likely focus on the engine’s maintenance history, potential foreign object debris (FOD) ingestion, and the performance of the aircraft’s internal fire suppression systems.
Frequently Asked Questions
What flight was involved in the Delhi airport incident?
The incident involved SWISS International Air Lines flight LX 147, which was operating a scheduled passenger service from New Delhi (DEL) to Zurich (ZRH) on April 26, 2026.
What caused the emergency evacuation?
The Airbus A330 experienced a severe engine failure and subsequent fire on its number one (left) engine during the takeoff roll, prompting the crew to abort the takeoff and evacuate the aircraft.
How fast was the aircraft traveling when the takeoff was aborted?
According to flight tracking data cited by the Times of India, the aircraft had reached a speed of 104 knots when the engine failure occurred.
Were there any injuries during the incident?
Yes. According to reporting by the Times of India, six passengers were hospitalized with injuries sustained during the emergency slide evacuation.
Did the incident close Delhi Airport?
While Runway 28 was closed to handle the emergency and remove the disabled aircraft, Delhi Airport officials stated that overall airport operations remained unaffected.
Sources
Sources: Times of India
Photo Credit: X
Regulations & Safety
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation6 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing5 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation5 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record
