Delta Boeing 767 Makes Emergency Landing After Engine Catches Fire Post Take-Off.
A Delta Air Lines flight bound for Atlanta was forced to make an emergency landing back at Los Angeles International Airport (LAX) on Friday after its left engine reportedly caught fire shortly after take-off. Flight DL446, operated by a Boeing 767-400 (registration N836MH), had just departed LAX when flames were seen coming from the aircraft’s left engine, according to eyewitness video. The incident occurred while the plane was climbing over the Pacific before it circled back inland for an emergency landing.
Fortunately, all passengers and crew on board were unharmed. Fire crews responded quickly and extinguished the fire once the aircraft landed safely on the runway.
According to flight data from Flightradar24, the aircraft flew a holding pattern over the Downey and Paramount areas to give the crew time to run safety checklists and coordinate the return with air traffic control. The flight maintained a stable altitude and speed throughout the emergency maneuver.
Passengers reported hearing an announcement from the captain informing them that fire crews were on the ground to verify whether the engine fire had been fully extinguished. A Delta spokesperson confirmed the incident, saying: “Delta flight 446 returned to Los Angeles shortly after departure following an indication of an issue with the aircraft’s left engine.”
The Boeing 767 involved is nearly 25 years old and is powered by General Electric CF6 engines. The exact cause of the fire remains unknown, and the U.S. Federal Aviation Administration (FAA) has launched an investigation. This is the second fire-related incident involving a Delta aircraft this year. In April, Delta Flight 1213 experienced an engine fire on the ramp at Orlando International Airport while preparing for takeoff to Atlanta. That aircraft, an Airbus A330, had 282 passengers on board at the time. No injuries were reported in that case either.
The FAA’s investigation will likely focus on the engine’s condition, maintenance history, and any technical malfunctions that may have contributed to Friday’s incident.
Comments are closed.