United Airlines flight forced to turn back to Heathrow as ‘fumes' fill part of plane after take-off
Flight UA949 took off from London Heathrow at 12.45pm on Wednesday 30 July for an 11-hour flight to the Californian city.
The Boeing 777 managed only 27 minutes in the air before unexpectedly returning to its departure base.
The plane reached as far as Milton Keynes, then ditched its flight path and looped back to London, flight tracking data shows.
United Airlines told The Independent: 'United flight 949 from London Heathrow to San Francisco returned to London shortly after take-off to address fumes in the aircraft's galley.'
The galley is the area in which cabin crew prepare food and store trolleys, and is where the toilets are typically found.
'The flight landed safely, passengers deplaned normally at the gate, and we're working to get our customers to their destinations as soon as possible.'
After landing, three fire engines met the plane on the taxiway. There were 272 passengers onboard at the time, along with 13 crew members.
Heathrow airport confirmed that the plane landed safely and did not have a wider impact on flight operations that day.
After the diversion back to the airport, the flight was ultimately cancelled. The aircraft is still at London Heathrow and is expected to take off at 8.50pm on Thursday 31 July, FlightRadar shows.
Heathrow, along with all other UK airports, were disrupted yesterday due to an unrelated air traffic control issue.
The incident comes just days after another United Airlines flight was forced to immediately divert back to Washington Dulles Airport after a mechanical issue.
The Munich-bound flight took off at 5.40pm local time on Friday, 25 July, yet circled back to the airport moments later.
The airline confirmed that the flight returned to the ground shortly after take-off to 'address a mechanical issue'.
All 219 passengers and 11 crew members deplaned as normal at the gate after the aircraft landed safely.
'The flight was subsequently cancelled, and we arranged alternate travel arrangements to take customers to their destination as soon as possible,' a spokesperson for the airline added.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Yahoo
an hour ago
- Yahoo
Wildlife refuge seeks volunteers to foster creatures with bad rep: 'They're wonderful garbage cleaners and gardeners' friends'
Wildlife refuge seeks volunteers to foster creatures with bad rep: 'They're wonderful garbage cleaners and gardeners' friends' If you live in the San Francisco Bay area and find small marsupials charming, local wildlife rehabilitators have excellent news. Yggdrasil Urban Wildlife Rescue was founded in 2001 after neighborhood children discovered several orphaned baby opossums — also known as "joeys" — left to fend for themselves in their deceased mother's pouch. That incident led its founders to discover that not only was the closest rescue organization 30 miles away, but also that most animals found in distress in the urban setting were euthanized due to a lack of resources. Founder Lila Travis decided to take action with her husband, and Yggdrasil Urban Wildlife Rescue started small in August 2002. It began with opossums, which makes it fitting that the creatures are why the organization came to widespread attention recently. On July 16, KGO-TV covered a call to action issued by the wildlife rescue center, seeking locals who care about animals to help foster an influx of baby opossums. At the end of June, Yggdrasil Urban Wildlife Rescue shared a plea on Facebook, seeking volunteers to foster and eventually release juvenile opossums with their "ReWild" team, all necessary training included. "We are 100% volunteer run. We need volunteers to be able to help these animals," Travis said. She also acknowledged opossums have a bad reputation, adding that while people inaccurately conflate them with rats, they actually "eat rats." "Opossums have a wonderful role in our environment. They're wonderful garbage cleaners and gardeners' friends," Travis continued, before explaining why this time of year is hard on them. She indicated the Fourth of July is like "Armageddon to them," one of several inhospitable conditions for opossums in the summer. Wildfires, increased human activity outdoors, and fireworks "can all lead to wildlife displacement," per KGO-TV. Volunteer Kitty Jones expressed a preference for the outcasts of the animal kingdom, which is why she's fostered "opossum after opossum" and "litter after litter" since she began working with the group. Would you take a gardening class if it were free? Heck yes! If it fits into my schedule Maybe Probably not Click your choice to see results and speak your mind. "It makes me really happy. They got to be free," Jones recalled of a litter she'd recently released into the wild. Of course, not everyone has the time or space to foster distressed wildlife, but donating to environmental causes is another way to get involved. Just under a week after KGO-TV profiled Yggdrasil Urban Wildlife Rescue's opossum fostering initiative, the organization shared an uplifting Facebook update. "We are so grateful and humbled — and amazed by the more than 200 volunteer applications we have received so far," they said. Those who wish to help but aren't local can also assist by purchasing items from Yggdrasil Urban Wildlife Rescue's Amazon Wish List. Join our free newsletter for good news and useful tips, and don't miss this cool list of easy ways to help yourself while helping the planet. Solve the daily Crossword
Yahoo
3 hours ago
- Yahoo
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter's altimeter was wrong The helicopter was flying at 278 feet (85 meters) — well above the 200-foot (61-meter) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 meters) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-meter) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 meters) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. FAA and Army defend actions, shift blame Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 meters) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. FAA was warned about the dangers of helicopter traffic in D.C. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.'' ___ Associated Press writer Leah Askarinam contributed. Josh Funk, The Associated Press Sign in to access your portfolio
Associated Press
3 hours ago
- Associated Press
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter's altimeter was wrong The helicopter was flying at 278 feet (85 meters) — well above the 200-foot (61-meter) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 meters) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-meter) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 meters) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. FAA and Army defend actions, shift blame Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 meters) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. FAA was warned about the dangers of helicopter traffic in D.C. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.'' ___ Associated Press writer Leah Askarinam contributed.
