San Diego plane crash killed multiple musicians: What we know about it
The impact of the crash also set ablaze multiple homes and vehicles, and forced evacuations across several blocks in the area. The pilot and passengers including multiple up and coming musicians died, but no one on the ground was killed or seriously injured.
The Federal Aviation Administration (FAA) confirmed the aircraft was a Cessna 550, which typically carries six to eight people. The incident occurred in the Murphy Canyon neighbourhood, just 3 kilometres from Montgomery-Gibbs Executive Airport.
The twin-engine Cessna 550 Citation took off from New Jersey, stopping for fuel in Kansas before heading toward San Diego. It crashed after clipping power lines in thick fog around 10.30 pm. Although eight people on the ground sustained injuries, none were serious.
The pilot had acknowledged poor weather conditions during communication with air traffic control. In audio shared by LiveATC.net, the pilot is heard contemplating a diversion: 'Doesn't sound great, but we'll give it a go,' he said.
The Federal Aviation Administration had issued a notice that the airport's runway lights were not operational at the time. The pilot didn't mention this to air traffic control but acknowledged being aware that the weather alert system was down.
Thick fog had reduced visibility to near zero, according to Assistant Fire Chief Dan Eddy. 'You could barely see in front of you.'
This crash adds to a series of fatal aviation incidents in the US in the recent times. Earlier this year, a collision between a passenger jet and an Army helicopter in Washington claimed 67 lives—the deadliest crash in more than two decades. Several smaller aircraft incidents across Alaska, Philadelphia, and the Hudson River have also taken place.
(With inputs from AP)
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
NDTV
3 hours ago
- NDTV
Night Vision Goggles May Have Hampered Chopper Pilots Before Crash With Jet: Experts
The pilots of a US Army helicopter that collided with a passenger jet over Washington in January would've had difficulty spotting the plane while wearing night vision goggles, experts told the National Transportation Safety Board on Friday. The Army goggles would have made it difficult to see the plane's colored lights, which might have helped the Black Hawk determine the plane's direction. The goggles also limited the pilots' peripheral vision as they flew near Ronald Reagan Washington National Airport. The challenges posed by night-vision goggles were discussed at the NTSB's third and final day of public testimony over the fatal midair crash, which killed all 67 people aboard both aircraft. Experts said another challenge that evening was distinguishing the plane from lights on the ground while the two aircraft were on a collision course. Plus, the helicopter pilots may not have known where to look for a plane that was landing on a secondary runway that most planes didn't use. "Knowing where to look. That's key," said Stephen Casner, an expert in human factors who used to work at NASA. Two previous days of testimony underscored a number of factors that likely contributed to the collision, prompting Board Chairwoman Jennifer Homendy to urge the Federal Aviation Administration to "do better" as she pointed to warnings the agency had ignored years earlier. Some of the major issues that have emerged so far include the Black Hawk helicopter flying above prescribed levels near the airport, as well as the warnings to FAA officials for years about the hazards related to the heavy chopper traffic there. It's too early for the board to identify what exactly caused the crash. A final report from the board won't come until next year. But it became clear this week how small a margin of error there was for helicopters flying the route the Black Hawk took the night of the nation's deadliest plane crash since November 2001. The American Airlines jet arrived from Wichita, Kansas, carrying, among others, a group of elite young figure skaters, their parents and coaches, and four union steamfitters from the Washington area. The January collision was the first in a string of crashes and near misses this year that have alarmed officials and the travelling public, despite statistics that still show flying remains the safest form of transportation. Tim Lilley, an aviation expert whose son Sam was a pilot on the passenger jet, said he's optimistic the tragic accident will ultimately lead to some positive changes. "But we've got a long way to go," he told The Associated Press. Lilley said he was particularly struck by the FAA's lack of alcohol testing for air traffic controllers after the crash. "That's pretty disturbing because that's automatic in aviation," Lilly said. "Everybody knows if there's a serious incident, you go to alcohol testing. And they made a bunch of excuses why they didn't do it. None of them were valid. It goes back to a whole system that was complacent and was normalizing deviation." Homendy brought up the lack of alcohol testing during Thursday's hearings, noting that it's most effective within two hours of a crash and can be administered within eight hours. Nick Fuller, the FAA's acting deputy chief operating officer of operations, testified that the controllers weren't tested for alcohol because the agency did not immediately believe the crash was fatal. The FAA then decided to forgo it because the optimum two-hour window had passed. NTSB board member Todd Inman pushed back, telling Fuller that the first two fatalities were confirmed 20 minutes after the crash. "How can you tell me that you released those controllers at midnight, but you didn't know a fatality occurred?" Inman said. Fuller said the FAA officials who make the determination on alcohol testing had not yet had confirmation on fatalities. Fuller said the agency is taking corrective steps and that its drug and alcohol testing process is now being revised. Rick Dressler, an official with medevac operator Metro Aviation, told the board on Thursday it is difficult to identify other aircraft in the night sky around Reagan National, especially if a key onboard locator system was switched off, as Army choppers routinely did. Dressler said that he and other civilian helicopter pilots in the area have long been concerned about the Army and Air Force helicopters flying around Reagan Airport. "I don't like saying this. I'll say it again on the record," Dressler, a former Army aviator and retired Air Force officer, said. "I'm speaking for my group there. We are all very uncomfortable when those two units are operating." The Department of Defense referred questions about Thursday's testimony to the Army, which did not immediately respond. Army officials at the hearing did ask Dressler to elaborate on his concerns and consider visiting the Pentagon to share them. Dressel said part of what worries him is the relative lack of experience of the military pilots who may have only been in the area a short time and don't understand the complex airspace around Washington, DC "They don't get the seasoning here to really, truly understand how the airspace works," said Dressel, who also complained that the Army helicopter unit no longer participates in regular meetings with all the other aviators in the area to discuss issues. The Air Force also did not immediately respond to questions about Dressler's remarks. Hearing testimony has covered much ground, including the final audio communications from pilots aboard the Army chopper. The Black Hawk's crew had been communicating with the airport's control tower, although the helicopter pilots did not fully hear the controller's instructions. The Black Hawk pilots told the tower twice in the minutes before the crash that they had the American Airlines passenger plane in sight and would maintain proper distance. But when the controller instructed the pilots to "pass behind" the jet, the crew didn't hear that instruction because the Black Hawk's microphone key was pressed at that moment. Just before the collision, an instructor pilot aboard the helicopter asked the pilot at the controls to come left. But it wasn't clear if the pilot had time to maneuver the helicopter before the crash. "Kinda come left for me, ma'am," the instructor said. The pilot responded: "Sure." John Cox, an aviation safety expert and retired airline pilot, said the hearings are headed in the right direction to determine what happened and to prevent similar accidents. His main concerns focus on the Black Hawk helicopter, including why it was above the 200-feet (61 meters) elevation limit for that particular helicopter route. Another question is why the Black Hawk wasn't closer to the east bank of the Potomac River, where it would have been further away from landing airplanes. "I've passed helicopters underneath me over the east bank of the Potomac a lot of times," said Cox, who flew commercial airliners for 25 years. "And there's always been plenty of separation. It's not a lot because the space is so constrained. But you're dealing with professional pilots, and it's not been a problem." Investigators said Wednesday the flight data recorder showed the helicopter was actually 80 feet to 100 feet (24 to 30 meters) higher than the barometric altimeter the pilots relied upon showed they were flying.
Time of India
5 days ago
- Time of India
Passenger Films Panic: American Airlines Jet Catches Fire, Chaos Caught on Selfie Video
A terrifying moment on an American Airlines flight went viral when passenger Shay Armistead filmed herself as smoke and flames filled the cabin. Her shaky voice saying, 'Plane just caught fire,' was heard just before the crew shouted 'Evacuate!' Chaos followed as she and others jumped down the emergency slide in Denver, with some falling hard on the runway. Parents clutched their kids, voices screamed for help, and firefighters rushed to the scene. The FAA is now investigating, and the airline confirmed the fire was caused by a tire malfunction on a Boeing 737 MAX 8. Thankfully, all 173 passengers and 6 crew members got out safely. Read More
NDTV
5 days ago
- NDTV
'Don't Be Like This Father': Man faces Flak For Saving Luggage 'Before Kid' As Plane Catches Fire
After an American Airlines flight was forced to abort takeoff at the Denver airport, owing to a landing gear malfunction, video footage of passengers sliding down the emergency exit have gone viral on social media. In one of the clips, a passenger can be seen prioritising his luggage over their child whilst evacuating the burning plane. After a few passengers had already evacuated, the man sat on the slide with the luggage in one hand and the child clinging tightly to him. As he attempted to stand up after sliding down, the weight and momentum of the luggage resulted in him falling over. Fortunately, the man fell on his back and avoided serious injuries to the child. However, as the video went viral, social media users reacted angrily at him for trying to fetch luggage in an emergency situation and jeopardising the lives of others. "Please don't be like this father focus on your child instead of your luggage. You can't safely manage both, and it only leads to accidents, like the one that just happened putting others at risk too," said one user. Meanwhile, another added: "If we are evacuating and someone starts getting a bag - I am throwing hands." A third commented: "Don't they listen to the pre-flight safety instructions? In an emergency, you're told not to take personal baggage with you." See the viral clip here: 🚨 #UPDATE: Please don't be like this father focus on your child instead of your luggage. You can't safely manage both, and it only leads to accidents, like the one that just happened putting others at risk too — R A W S A L E R T S (@rawsalerts) July 26, 2025 Boeing plane catches fire Flight AA3023, a Boeing 737 MAX 8 aircraft bound for Miami, was on the runway, ready to depart, when the fire was spotted. The aircraft reported a possible landing gear incident while departing from the Denver airport around 2:45 pm (local time), said the Federal Aviation Administration (FAA), adding that the passengers were evacuated on the runway and transported to the terminal by bus. All 173 passengers and six crew members were safely evacuated, though one individual was transported to the hospital for further evaluation
