Delta's Boeing 767 makes emergency landing in Los Angeles as engine catches fire moments after takeoff
The video shows flames emanating from one side of the aircraft. No one was injured. The fire was extinguished upon landing.
According to a report by Aviation A2Z, the plane (24-year-old Boeing 767-400 with registration N836MH) had just departed from Los Angeles International Airport (LAX) when its left engine ignited. The pilots promptly declared an emergency and requested to return to the airport. Air Traffic Control (ATC) provided guidance for the aircraft to head back to LAX and notified ground emergency crews.
Data from Flightradar24 indicates that flight DL446 ascended over the Pacific Ocean before redirecting inland, flying over the areas of Downey and Paramount. This route allowed the flight crew to carry out necessary safety protocols and get ready for landing. Throughout the maneuver, the plane held a consistent altitude and airspeed.
'Delta flight 446 returned to Los Angeles shortly after departure following an indication of an issue with the aircraft's left engine," BBC quoted a Delta Air Lines spokesperson as saying. According to passengers, the captain told them that fire crews were 'verifying that the engine fire is out'.
The Federal Aviation Administration (FAA) has initiated a probe to assess the fire cause. The plane is equipped with two General Electric CF6 engines, reports said.
In April, a separate Delta aircraft encountered an engine fire at Orlando International Airport. Delta Air Lines Flight 1213 was getting ready to depart for Atlanta when the fire erupted on the ramp. The aircraft involved, an Airbus A330, had 282 passengers on board, along with 10 flight attendants and two pilots. Everyone was safely evacuated, and no injuries occurred.
Emergency response and firefighting units at Orlando airport acted swiftly to manage the incident.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
News18
14 hours ago
- News18
Three Killed After Private Plane Crashes Off Monterey Bay In California
The crash site was approximately 300 yards (about 275 metres) off the coast of Point Pinos in Monterey County. Three individuals on board a small private aircraft were found dead after the plane crashed into the waters off Monterey Bay, California, as reported by Associated Press. According to the US Coast Guard, the victims were located unresponsive on the morning of Sunday, July 27. Emergency crews had responded to the scene the night before, shortly after the crash occurred. The aircraft involved was identified as a Beech 95-B55 Baron, a twin-engine light plane. It departed from San Carlos Airport at 10:11 pm local time. However, the flight was abruptly cut short, with its final recorded location logged near Monterey at 10:37 pm, according to flight tracking platform Flightradar24. The plane bore the tail number N8796R. The crash site was approximately 300 yards (about 275 metres) off the coast of Point Pinos in Monterey County. Witnesses reported hearing the sound of the aircraft's engine revving, followed by a loud splash in the water. Debris from the aircraft was later spotted floating near the shoreline, as reported by KSBW-TV. Following the initial reports, the US Coast Guard, in coordination with local fire departments and law enforcement agencies, launched an immediate search and rescue operation using both boats and helicopters. At around 3:00 am, the first individual was discovered on the water by a Coast Guard boat crew. Later, divers located the other two missing passengers inside the submerged wreckage between 6:30 am and 9:30 am. 'At the time of recovery, all three individuals were unresponsive," said Petty Officer Ryan Graves in a statement to the Associated Press. 'In this case, unresponsive means no signs of life. However, it is the coroner's office and Sheriff's office that officially determine death." The three victims were later identified as Steve Clatterbuck, 60, James Vincent, 36, and Jamie Tabscott, 44. James and Jamie were local residents of Monterey. The exact cause of the crash, as well as the sequence of events leading up to the incident, remains under investigation. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) will lead the inquiry into the accident. Get breaking news, in-depth analysis, and expert perspectives on everything from geopolitics to diplomacy and global trends. Stay informed with the latest world news only on News18. Download the News18 App to stay updated! Location : California, USA First Published:
News18
a day ago
- News18
Kolkata: New Garia Metro Shut For 6 Months, What Went Wrong At The Key Interchange?
Last Updated: Though the station was built just 15 years ago, some officials admitted there were already 'red flags' in the structure's design before the damage. Metro services to Kavi Subhash (New Garia) station came to a grinding halt on Monday after visible cracks were found in the support columns of the station platform. The cracks appeared on the Up platform, which serves Dakshineswar-bound trains on the Blue Line. As per Telegraph India, metro authorities suspect the damage was caused by 'uneven settlement" due to recent heavy rainfall. As a safety measure, services to and from the terminal station have been indefinitely suspended. How Long Will the Repair Take? While an official timeline hasn't been confirmed, sources within Metro Railway say it could take at least six months before the station is operational again. A detailed assessment is underway, and repair work will begin soon. In the meantime, Blue Line trains will run only between Dakshineswar and Shahid Khudiram (Dhalai Bridge). Though the Orange Line—from Ruby to New Garia—remains unaffected, the crucial interchange at New Garia is now non-functional, causing major inconvenience. What's the Bigger Concern? Some Metro officials believe the station's design did not consider the soil type adequately. Cracks were reportedly noticed even before the rains, suggesting deeper structural flaws. Why Does This Matter to Commuters? The closure impacts thousands. New Garia station connects directly with the suburban railway network, allowing seamless transfers. With several new housing projects in areas like Narendrapur and Panchasayar, ridership from New Garia had seen a steady rise. 'This shutdown has messed up my daily commute," said Sameer Guha, a regular commuter. 'It's shocking that such a new station is crumbling." view comments Disclaimer: Comments reflect users' views, not News18's. Please keep discussions respectful and constructive. Abusive, defamatory, or illegal comments will be removed. News18 may disable any comment at its discretion. By posting, you agree to our Terms of Use and Privacy Policy.
The Print
a day ago
- The Print
‘More careful than colourful'—ThePrint's reporting on the Air India crash put facts first
This Readers Editor column considers ThePrint's approach to its reporting on AI-171 and the subsequent preliminary findings of the investigation by the Aircraft Accident Investigation Bureau (AIBB) released on 12 July 2025. When you're reporting on something as devastating, sensitive—and immediate—as the Air India-171 crash last month, it is crucial to remember the value of good journalism, amid the endless theories on the reasons for the accident. Good journalism requires good hygiene. That means you have to write clean copy and provide the audience with a clear picture of the events you report. You have to cut out all the frills, the speculation, the 'extras'—which might make your reporting more lively and interesting to read, but don't always give readers accurate, factual, verified information. ThePrint's coverage was descriptive but factual and based on reliable sources. When you go through the articles or watch the videos, you will notice that the reporters are being selective in their choice of words. After reading or watching most of the reporting, I'd say it was more careful than colourful. The day of crash The afternoon of 12 June was just another normal day at ThePrint. I remember that it was a Thursday because I was at ThePrint's office in New Delhi for my weekly meeting with colleagues. It was fairly quiet as afternoons go, with reporters out on assignments, and those in the office staring at the computer monitors or mobile phones. Suddenly, it came to life. I saw people rush to watch the television monitors, and as I joined them, I beheld a sea of serious faces around me. The AI-171 had crash-landed at Ahmedabad airport. Nisheeth Upadhyay, Editor News Operations, realised it was huge. 'Whenever a commercial flight crashes it is a huge deal. We knew this was a big story.' The immediate response was to put out a 'Breaking News' story with the little information available. Next was to check for an accurate reading of the flight's movements up to its fall to the ground. Since I don't work on the editorial side of operations at ThePrint, I began to feel a little redundant, and in people's way. So, I sat on the sidelines and watched. A quick edit meeting was convened and everyone present in the office came together to suggest immediate story ideas. 'We felt, instinctively, that we should report the news as it came through and could be confirmed, but also do stories that added value,' Upadhyay said. 'From the moment it happened, there was so much noise in the media and social media—everyone was playing expert. 'At ThePrint, we were clear: Be sensitive, give the information, don't analyse—just plain, simple facts and information that can be confirmed. No conjecture.'' The difficulty that arose was the lack of access to the facts of the accident—or to any immediate information from the site of the crash in Ahmedabad—ThePrint doesn't have its own correspondent in the Gujarat capital. In stepped, Rama Lakshmi, Editor, Opinion and Ground Reports, and her team to fill the void. 'We had to keep reader interest going,' said Lakshmi. She also had previous experience covering airplane crashes, which helped. 'I put on my reporter's cap and looked for different angles to the story until our reporters reached the accident spot,'' she added. The reporters in the Delhi Ground Reports team filed reports on past history and the context of the incident. From other commercial flight crashes in India and Air India's current fleet of aircraft, accounts of survivors in Ahmedabad, stories of people who suffered in similar plan crashes, to another sole survivor of an air crash, the revamp of Ahmedabad runway, and the last social media post of some victims—these were some of the early stories put out by ThePrint. Interviewing victims & tackling misinformation The most pressing concern was to get on-ground reporting from Ahmedabad. ThePrint's nearest reporting team was in Mumbai. 'We were unsure of flights taking off from Mumbai and being able to land in Ahmedabad,' recalled Manasi Phadke, Deputy Editor based in Mumbai, who reached the city the next morning. Luckily, the Delhi-Ahmedabad evening flight was on schedule, so National Photo editor Praveen Jain and Senior Correspondent Krishan Murari flew out. 'I have covered earlier air crashes—Charkhi Dadri, for example. So I knew what it was like on the ground,' said Jain. In 1996, a midair collision between two commercial aircraft over Charkhi Dadri outside Delhi killed 349 people. Krishan Murari had never reported on an air crash or any accident of this proportion. He'd reported on Operation Sindoor and the Pahalgam terrorist attack in May. AI-171 presented a different challenge. 'After Operation Sindoor, coming to this, I realised you need a completely different kind of vocabulary. You have to be far more sensitive. I'd call it compassionate journalism,' he said. Praveen Jain and Krishan Murari reached Ahmedabad within 12 hours of the crash and visited the site, the hospital, and the mortuary. 'It was very hot outside, and even inside, the temperature was higher than it should have been. There was an overwhelming smell of the charred bodies,' Murari added. Together, they filed a number of stories over the next few days. Here are some of them: Meet the forensic dentist racing against time so kin of Air India crash victims can say final goodbye Air India crash: Inside Ahmedabad hospital morgue, bodies await DNA ID as doctors race against heat, time Confusion, debris & bodies at Air India crash site. Rescue worker first thought it was cylinder blast Air India crash: All 4 hostel buildings of BJ Medical College emptied amid site investigation This Air India crash eyewitness cheated death by a whisker—'a blast, then a fireball, just 200 m away' Manasi Phadke found the lack of official information to be one of the major stumbling blocks in her first few days of reporting. 'The media was the least important for them, so we had to source information wherever we could,'' she said, 'We had to be very careful, not speculate.' So, she had to piece together information. Here are some of the stories she filed: 11 DNA matches 48 hrs after Air India crash: Process of releasing victims' bodies to families begins The crash, the rescue & aftermath—Inside the first 36 hours at ground zero of Air India crash Behind the scenes of Gujarat's Air India crash response—4 IAS officers, 36 DNA experts & 230 teams Medical college's exam hall turns into DNA sampling centre. For victims' kin, it's the longest test yet After a week's search, family working in hostel mess cremates mother & 2-yr-old killed in Air India crash Phadke, Jain and Murari turned to doctors, workers, and the families of the victims. 'Families presented a challenge, a lot of them were angry. You can't just walk up to them and say, 'Kya hua?'. 'We had to be sensitive—I didn't use the camera immediately—I waited till they were at ease,' recalled Praveen Jain. As far as possible, he tried to click pictures from a distance. Even, then, one family member of a victim scolded him for taking pictures and Jain immediately apologised. Phadke said she had to make people feel comfortable before they spoke. Some like to speak – 'I am still in touch with at least one relative,' she said, adding, 'You have to talk around the subject, be conversational.' Also read: Inside ThePrint's mailbox—readers bring us praise, critique, and everything in between Unpacking investigation report Back in Delhi, Bismee Taskin, Principal Correspondent, was keeping an eye out for government communications. 'My job was to get in touch with the DGCA, the civil aviation ministry. To confirm information, verify it with at least two reliable sources,' she explained. She was also in touch with former pilots of Air India. When the preliminary report was released on 12 July, she reported it. 'Preliminary report is like an FIR,' said Taskin, 'No conclusions should be based on it. You have to wait till the final report for probable cause.' Taskin's stories, therefore, were straightforward, simply putting out what the report stated. Have a look: Air India crash spotlights 2018 advisory on Boeing switches installed with locking feature disengaged Air India crash preliminary report: A look at what fuel switches are designed to do & built-in safeguards Throughout the last month and a half, victims' families, aviation experts and the average reader want to know what brought the aircraft down? Why did it crash? There are so many technical details to it—and a lay person, with no understanding of them was prey to various theories doing the rounds. Nisheeth Upadhyay is, in his own words, an 'aviation nut''. Thus, it was possible for him to understand the complex (mal)functioning of an aircraft and to explain it in simple language. 'I was very careful not to act as an authority on the subject, just to describe what we knew had happened and to explain,'' he said, 'No aviation experting.'' On the preliminary report, which led to so much speculation and finger-pointing to pilot error in some foreign news media such as the Wall Street Journal, Upadhyay said only the final report mattered: 'There is not enough evidence to attribute blame. And so, ThePrint's line was that—there's not enough information to reach a conclusion.' I would recommend you watch his videos: they are clear, concise, and to the point, factual—without unnecessary opinion or speculation. I know I learned a great deal from them. The common thread in ThePrint's reporting—from the ground and Delhi—was to keep it simple, stick to verified facts and attribute views clearly. I have one suggestion newsrooms like ThePrint could consider: After tough assignments in the field, reporters may need some assistance in dealing with the traumas they witness. It can be overwhelming, especially for young reporters. Counselling is one option, and a few days' leave may help them cope better. Shailaja Bajpai is ThePrint's Readers' Editor. Please write in with your views and complaints to (Edited by Ratan Priya)
