Southwest flight from Burbank drops hundreds of feet to avoid possible collision
The plane was at 14,100 feet above Angeles National Forest headed northeast to Las Vegas at 12:03 p.m. when it abruptly dropped to 13,625 feet, data from Flightradar24 showed.
The drop of around 500 feet came moments after the plane had been gaining altitude steadily since takeoff, causing tense moments on the plane. Passengers said on social media that they were startled by the move.
Steve Ulasewicz, 33, was on the plane. The Woodland Hills resident felt a sudden drop around eight minutes into the flight, and thought it might be bad turbulence.
After a two- or three-second pause, the plane went into "free fall for about eight to 10 seconds," he said. "People were screaming. I felt my body come up and out of the chair."
In a lifetime of flying, he had never felt anything like it. 'I thought that was it — I thought we were all dead,' he said. 'I don't want to die,' Ulasewicz told his friend sitting nearby during the fall.
After the plane leveled out, passengers were confused. Ulasewicz wondered if there was a bird strike or mechanical issue. He waited the "longest two to three minutes of [his] life" before the pilot came on the intercom to announce the near collision, he said.
He saw a female attendant with an ice pack on her head. Unlike the passengers, she was not buckled in during the ascent as she prepared to serve beverages.
After the terror of the incident, Ulasewicz said the revelation that his plane was involved in a near miss changed his emotions to anger. He listed off a number of similar incidents in U.S. skies in recent months.
The commercial flight had to climb and descend to comply with two onboard traffic alerts, Southwest spokesperson Lynn Lunsford said in a statement to The Times.
"The flight continued to Las Vegas, where it landed uneventfully," the statement said. "Southwest is engaged with the Federal Aviation Administration to further understand the circumstances."
"No injuries were immediately reported by Customers, but two Flight Attendants are being treated for injuries," Lunsford said.
The Federal Aviation Administration said it was investigating the incident in a written statement.
A military jet was headed southwest to Naval Base Ventura County in Point Mugu and was at a similar altitude — 14,525 feet — when the Southwest flight dropped, per Flightradar24.
The planes were around five miles apart and within 400 vertical feet of one another, headed in opposite directions, when the Southwest flight took evasive action, flight data on the website showed. The fighter jet stopped its own steady descent and maintained its height for several minutes after the incident.
The plane landed in Las Vegas at 12:39 p.m. Friday.
There has been growing focus on aviation safety in recent months.
A series of radar outages at Newark Liberty International Airport brought massive flight delays in May. Federal officials continue to investigate the January collision in Washington between a commercial jet and a military helicopter that killed 67 people.
In San Diego, a private jet crashed, killing all six on board, in June. A federal investigation found the aircraft was flying too low before it hit power lines and slammed into a house.
The automated system that provides weather conditions and runway lights weren't operating at the airport before the plane crashed, the report confirmed.
This is a developing story and will be updated.
Sign up for Essential California for news, features and recommendations from the L.A. Times and beyond in your inbox six days a week.
This story originally appeared in Los Angeles Times.
Solve the daily Crossword
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
CNN
12 hours ago
- CNN
NTSB probes collision avoidance technology, safety systems in final day of midair collision investigative hearings
In more than 32 hours of testimony across three days the National Transportation Safety Board probed virtually every detail of what led up to the January 29 midair collision between a US Army Black Hawk helicopter and an American Airlines regional jet, operated by PSA airlines. The focus Friday evening was the many organizational structures that may have impacted the deadly collision, which killed 67 people over the Potomac River, near Ronald Reagan Washington National Airport. 'I don't think the accident occurred that night. I think it happened years before,' Clark Allen, Air Traffic Control Specialist at the Federal Aviation Administration said. 'It was a combination of many years that built up to that evening.' After the collision, the FAA replaced many of the air traffic control managers with responsibility for the Reagan National Airport area 'in what appears to be blame and even punishment or retribution, in their eyes,' NTSB investigator Brian Soper noted Friday. 'It's always struck me how many times that as soon as we announce a launch (of an investigation)… the air traffic manager and or key management personnel are often relieved, moved, changed out sometimes, right while we're on site.' The general manager and assistant general managers from the Washington district as well as the air traffic manager and operations manager from the airport control tower were removed, he said, 'effectively removing all of the institutional knowledge at the management level.' 'So we didn't remove anybody as a result of an accident,' Nick Fuller, FAA Deputy Chief Operating Officer of Operations, noted. 'You didn't?' Jennifer Homendy, NTSB chair asked skeptically. 'I think many would disagree, since it was done pretty immediately. Also, the NTSB had to weigh in several times to get people help in the tower.' 'Because what we're hearing is and seeing, and what they're seeing is the response is people get transferred or fired, or the safety culture team got removed,' she said. 'So we're trying to figure out, OK, that's the message they're hearing, which isn't good.' The new management team in charge of the Washington controllers had 'great resumes,' but 'don't have the skill set or the experience,' Soper said. 'Can you please help me understand how this will provide an orderly and safe transition to the new and still evolving operational procedures, a decrease in risk of reoccurrence and an increase in safety?' 'The individuals that were put into that place, as you said, their resumes were not just impeccable, but they've actually shown as proven leaders that can actually effectuate change in a positive manner and ensure that safety is not compromised,' Frank McIntosh, FAA Chief Operating Officer said. The NTSB noted an apparent communication breakdown between what controllers were saying and what witnesses in this week's hearing were saying. 'We're sitting here getting testimony 'we have done these great things, we've done these wonderful things.' The documents and the information and the facts that we have are not seeing that,' Inman said. 'There's a significant frustration between what's actually occurring being what's being said for public consumption.' 'I 100% agree with you. There definitely seems to be some barrier in communication where the people that impacts the most are not hearing the things that the FAA is moving forward on, and that needs to be addressed,' McIntosh responded. The questioning included probing organizational systems in place to manage risk, and NTSB board member Michael Graham noted the breakdowns were a failing of these essential programs. 'You don't have a safety management system if that person out on the leading edge, or in the control tower doesn't feel like they can report, they can be heard be responded to,' he said. 'For our system to be as safe as can be you have got to engage every employee.' Highlighting the frustrations, the NTSB noted their team was in the control tower facility in March when there was a fight between a traffic management coordinator and a controller. One employee was arrested at the time. NTSB chair Homendy was also highly critical of FAA not providing all of the data the board requested, citing back and forth requests for information the agency collected about close calls at airports. 'I think you are interfering with the investigation,' Homendy said. 'I want to hear 'great, let's work together.' I don't want to hear 'no' every time we ask for information.' She additionally noted the FAA provided different data to Congress than it gave to the NTSB. 'I'm not going to play the data game with you guys anymore,' she said. 'It's actually a well known thing that every time we come out with data you are going to come out with other data.' 'It just is not helpful. It just looks like you are trying to hide things, which I don't think you are,' she said. The FAA vowed to work together to get the information needed. 'The last thing we want is for there to be a feeling that we are not good partners when it comes to raising our safety standards,' McIntosh said. The airport, often called by its code DCA, is considered by the Federal Aviation Administration to be a 'special qualification airport' and anyone who flies there must undergo specific training due to the complex and challenging characteristics of the airspace. PSA pilots are all qualified to operate there and receive FAA-approved training, PSA's Assistant Director Flight Operations, Technical, Grant Clow testified. 'Think of it like a consolidated playbook of DCA-related guidance that we extract from all the different manuals and resources that we have as like an orientation guide for both new pilots and pilots that maybe have recently upgraded or have been away for a while to kind of re-familiarize themselves with information specific to DCA,' he said. However, neither this document nor any of the airline manuals provided to PSA pilots had information specifically describing helicopter operations or routes around at the airport at the time of the accident, according to Clow. The Army's reluctance to use an anti-collision technology known as Automatic Dependent Surveillance–Broadcast, or ADS-B, and why the FAA allowed military helicopter pilots to fly without it was a key topic of questioning Friday. 'ADS-B out' transmits radio signals with GPS location, altitude, ground speed and other data once per second, independent of air traffic control. However, on January 29, the Black Hawk was flying following an FAA memorandum which allowed it to be turned off. There are currently no rules stating the military must use the collision avoidance system nationwide, an FAA official testified, as ADS-B requirements are determined by location. Lt. Col. Paul Flanigen of the US Army said the Department of Defense has 'concerns' with the technology. 'I pretty sure most people are aware of the fact that it's inherently open source,' Flanigen testified. 'It has some spoofing vulnerabilities which make it non-conducive for those sensitive missions, which not just the Army, but all of DOD has to operate on.' Earlier this week, a bill was introduced that would require aircraft operators to install ADS-B technology on all flights and require the Army to keep it turned on in almost every case. The NTSB has also called for aircraft to be equipped with 'ADS-B in,' the ability to receive data from surrounding aircraft and display it on a cockpit screen for pilots. The NTSB can make recommendations, but it is up to the FAA to mandate something. On Friday, the FAA agreed it should be required, but stopped short of saying it will act on the issue. 'Does the FAA, right now, support requiring that any newly manufactured aircraft registered in the US be equipped with ADS-B in?' Homendy, the NTSB chair asked. 'Yes, ma'am,' McIntosh, the FAA chief operating officer replied. 'Do you also support or oppose requiring that any aircraft required to be equipped with ADS-B out today… also be required to install and operate ADS-B in?' Homendy followed up. 'Yes, ma'am,' McIntosh replied again. 'Your position has shifted, and I appreciate that,' Homendy said. The first two days of testimony highlighted critical moments leading up to the collision as investigators probed witnesses about standard safety practices that should have occurred, altimeters that displayed incorrect altitude, and the helicopter route that came perilously close to the path planes use landing at the airport. There were over ten hours of testimony on each of the first two days of the hearing. The NTSB asks questions, but parties to the investigation including the Army, PSA Airlines, air traffic controller's union and FAA can also examine witnesses. On Thursday, an FAA witness acknowledged the air traffic control tower failed to warn the pilots flying the American Airlines regional jet, operated by PSA Airlines. 'No safety alerts,' were given, Fuller, the FAA Deputy Chief Operating Officer of Operations, testified. 'Should the local controller have let the PSA crew know that there was a helicopter there?' Homendy asked. 'Yes,' Fuller acknowledged. The tower did warn the pilots of the Black Hawk helicopter about the approaching regional jet and they said they would avoid it, transcripts of the cockpit voice recorders and air traffic control audio released revealed. Yet, moments later, the aircraft collided. Multiple air traffic controllers and pilots at Reagan National Airport told the NTSB they struggled with the constant stream of planes, leading to a 'make it work' attitude among them. 'This is 'we just make it work,' because we don't have another choice,' NTSB investigator Brian Soper said they told him in on-site interviews. 'There are airplanes coming in and everything was related to the capacity, the demand or the amount of traffic.' Another witness, Rich Dressler of Metro Aviation, which operates medical helicopters in Washington said the way the Army flies helicopters around the city makes him uneasy. 'Is there any unit that when you hear it makes you feel uncomfortable?' Soper asked. 'Sadly, yes,' Dressler responded. 'I don't like saying that 12th aviation battalion gives us all pause in the community. And I'm speaking from my group there; we are all very uncomfortable when those two units are operating.' An NTSB determination of the collision's probable cause is expected in January.
CBS News
19 hours ago
- CBS News
Colorado firefighting plane makes emergency landing due to mechanical issue with landing gear
A firefighting plane in Colorado had to make an emergency landing without the landing gear working properly on Friday. According to the Colorado Department of Fire Prevention and Control, the Pilatus PC-12 Multi-Mission Aircraft was returning from a detection mission along the western slope when the flight crew discovered a problem with the plane's nose landing gear. They declared an emergency as a precautionary measure and brought the plane in to land at Grand Junction Regional Airport. Despite the nose landing gear not locking into place, they were able to execute a controlled landing, bringing the aircraft to a stop on the runway. Officials said that no one was injured during the incident. They said the emergency landing will be investigated according to FAA and NTSB protocols.
CBS News
a day ago
- CBS News
Key takeaways from 3-day hearing on deadly D.C. midair collision
Over the course of three days of investigative hearings, the National Transportation and Safety Board sought to gather more information about the factors that lead to the deadly midair collision over Washington, D.C., in January between an Army helicopter and a passenger plane. The NTSB heard testimony from air traffic controllers, the Federal Aviation Administration and the Army, and the families of several of the victims attended. At one point on the first day of the hearings, NTSB Chairwoman Jennifer Homendy said of the circumstances leading up to the crash, "Every sign was there that there was a safety risk." Addressing the families, she said the hearings would be "a critical part of our ongoing investigation." On Jan. 29, a Black Hawk helicopter struck an American Airlines flight from Wichita, Kansas, as it was coming in for a landing at Ronald Reagan National Airport, killing all 67 people aboard both aircraft. The NTSB will continue its fact finding and will compile a final report with determinations about the probable cause, likely within the next year. Here are the top takeaways from the hearings: The barometric altimeter the Black Hawk crew members were relying on may have given them incorrect information, according to NTSB investigators, because the crew was calling out altitudes that were lower than the actual height at which the helicopter was flying. The helicopter and commercial airliner collided approximately 300 feet above the Potomac River, and the maximum altitude for helicopters at that part of the route near D.C.'s Reagan Airport is 200 feet. The NTSB, as part of its investigation, tested three helicopters that are in the same battalion as the one that crashed and found that the barometric altimeter for all three was off by 80 to 130 feet. Army representatives on Wednesday told investigators that discrepancy is within the accepted variability because pilots are trained to maintain their altitude at plus or minus 100 feet. NTSB Chair Jennifer Homendy told CBS News' senior transportation correspondent Kris Van Cleave the NTSB calculated the margin of error on Route Four in that area of the Potomac to be 75 feet. The Army said it is conducting additional reviews to determine how to proceed, frustrating investigators who asked why it would not make changes to the equipment, based on the findings of the NTSB tests. In 2022, an FAA working group considered moving helicopter traffic away from the airport, but ultimately did not. Transcripts from the airplane's cockpit voice recorder show the pilots received an automated verbal warning about traffic in the vicinity approximately 20 seconds before the collision. Less than two seconds before impact, the pilots shouted in alarm. Flight data indicates the plane's pilots attempted to climb to avoid the helicopter just before impact. The transcripts also reveal the pilots of the American Airlines flight questioned the move to Runway 33. The plane was originally supposed to land on Runway 1 but was redirected by air traffic controllers to Runway 33. As it was trying to land on that runway, the helicopter and plane collided. The pilots of the Black Hawk missed a key word when communicating with the air traffic control tower, according to a transcript released during the hearings of the conversation between the helicopter crew and the control tower. Fifteen seconds before the collision, DCA Tower asked the helicopter if it had the regional jet in sight. Four seconds later, the DCA Tower instructed the helicopter to pass behind the plane. The Black Hawk's cockpit voice recorder indicated that the phrase "pass behind" was rendered inaudible because a helicopter crew member pressed the microphone key. Although it was already known — based on control tower audio from that night — that the controller did not warn the American Airlines plane that the Black Hawk might cross its path, the FAA only openly acknowledged this for the first time during this week's hearings. In a key moment from the second day, Homendy asked FAA Air Traffic Oversight Service executive director Nick Fuller if any traffic advisories or alerts were issued to the plane. He responded, "No safety alerts." Homendy then asked, "Should the local controller have let the [plane] crew know that there was a helicopter there?" "Yes," Fuller responded. Rick Dressler, of Metro Aviation – which operates medical helicopters — was asked if there are units flying in the National Airport airspace that make him uncomfortable. "I don't like saying that first heli of [U.S. Air Force] from Andrews (Air Base) and I don't like saying that 12th Aviation Battalion gives us all pause in the community…," Dressler said, but "we are all very uncomfortable when those two units are operating." During the hearing, the Army admitted helicopters regularly flew below flights that land at Reagan National Airport.
