Washington, DC
The National Transportation Safety Board convened a two day listening to on Tuesday to research why a UPS McDonnell Douglas MD-11F lost an engine and crashed after taking off final yr from Louisville, Kentucky.
“We issue safety recommendations … they are to be taken seriously,” stated Jennifer Homendy, chairwoman of the NTSB. “Those recommendations are aimed, they’re comprehensive, they’re extensive, and they’re aimed at preventing another tragedy. If they’re not implemented … we will be here again.”
On November 4, UPS flight 2976, a cargo plane headed to Hawaii, crashed moments after taking off from Louisville Muhammad Ali International Airport, spreading flames and wreckage for a half-mile and sending black smoke billowing into the sky. Fifteen people died, together with the three crew members on the aircraft, and one one who succumbed to their accidents 51 days after the crash. Twenty-three folks on the bottom had been injured.
The UPS freighter was a 34-year-old jet with three engines: two on the wings and one on the tail.
The listening to comes simply days after the Federal Aviation Administration cleared the identical kind of plane to return to the skies.
Now, the NTSB will query witnesses, together with representatives of UPS, the pilot’s union, the FAA and Boeing, to assist decide what went fallacious.
The chairwoman addressed the numerous members of the family of victims gathered Tuesday within the board room, expressing her condolences.
“This accident, just like others, undoubtedly caused invisible injuries that aren’t reflected in the numbers we provide,” Homendy stated. “Psychological and emotional trauma from being physically injured, witnessing an accident, or losing a loved one can have a profound impact on lives and livelihoods.”
Tuesday’s listening to is predicted to go for 10 hours. It will cowl fleet security processes, how anomalies discovered throughout upkeep are reported, the FAA and Boeing’s continued operational security program and communications after issues are discovered.
The company already decided a pair of structural fittings that stored the left jet engine connected to the wing broke, in keeping with the NTSB.
At Tuesday’s listening to, the board performed an animation of the engine-to-wing attachment design and the way it failed.
The engine is connected to the wing by a mount containing a spherical bearing, generally known as a bearing race, held inside structural brackets known as lugs. Investigators say the bearing race cracked from fatigue and cut up aside. That shifted irregular masses onto the lugs, which then fractured, permitting the engine to fall from the wing.
Investigators questioned whether or not the structural issues may have been caught earlier. There had been 9 reviews of bearing race issues earlier than the crash which Boeing analyzed, however decided the issues didn’t pose a security difficulty and the FAA didn’t require further inspections.
“We have a bearing fracture, and it slides out, it migrates a little bit,” stated David Springer, senior director of engineering and technical operations at UPS Airlines. “It’s not a big deal. The rest of the damage that was being caused was a big deal. I think if we would have known that at UPS, I think we would have asked a lot of different questions over the years.”
At the tip of the animation, an airport safety video confirmed the engine separating and going up and over the wing earlier than falling alongside the runway. The aircraft spewed fireplace and a darkish path of smoke on the runway because it descended to the bottom. The MD-11F solely received about 30 toes within the air earlier than crashing into a warehouse, storage yard, and petroleum recycling facility simply exterior the airport.
According to NTSB documents, the over 9 hour flight to Hawaii was initially meant to happen on a totally different aircraft.
However, a gas leak on the unique plane was “discovered and reported to maintenance” throughout a routine pre-flight inspection. The airplane that finally crashed was assigned to the crew as a alternative.
Three days after the crash, UPS grounded its MD-11 planes, and the next day the FAA grounded all MD-11 planes within the United States till inspections had been accomplished. At the time of the crash, MD-11 plane made up roughly 9% of UPS’ fleet, the carrier said. FedEx and Western Global Airlines additionally flew the identical kind of plane.
Last week, “after extensive review, the FAA approved Boeing’s protocol for safely returning MD-11 airplanes to service,” the company advised NCS in a assertion.
Boeing, which grew to become the producer chargeable for the MD-11s because it purchased McDonnell Douglas, has offered inspection and restore directions. Boeing “continues to provide technical support and guidance to help them meet FAA requirements,” a firm spokesperson advised NCS.
UPS introduced it doesn’t plan to fly its MD-11s any longer. Meanwhile, FedEx has already resumed some flights with repaired and inspected plane.
Following the grounding of MD-11 fleets, inspections revealed bearing race issues on three UPS MD-11Fs and one different, the NTSB stated.
“Had we known more, we could have done more with this,” stated Shannon Deckard, director of high quality assurance at UPS.
During this week’s hearings, extra particulars about what brought on the crash are anticipated to be made public.
All earlier upkeep will probably be reviewed, together with overhaul work completed for six weeks that the plane was out of service in September and October in San Antonio, Texas. The aircraft resumed flying for UPS lower than a month earlier than the crash.
The info from the cockpit voice recorder and flight knowledge recorder will point out what the pilots stated and how they reacted to the troubled flight.
Investigators will even probe what info UPS was required to report back to Boeing and the FAA, operational security course of and engine attachment designs.
A remaining report from the NTSB is usually anticipated in 18 to 24 months after an accident, detailing the possible causes of the crash. The company doesn’t place blame however determines what went fallacious and offers suggestions to enhance security.