Microscopic examination supports early suspicions that wear and tear caused a fan blade to snap inside one engine of a United Airlines plane that made an emergency landing shortly after takeoff last month in Denver, federal safety investigators said Friday.
The National Transportation Safety Board said the exam found “multiple fatigue fracture origins” on the inside surface of the hollow fan blade. The board said “multiple” secondary cracks were found, and that the examination is continuing.
The broken blade on the Pratt & Whitney engine had been used on 2,979 flights since its last inspection in 2016, the NTSB said. At the time, similar blades were required to be inspected every 6,500 flights. The NTSB believes the failed blade then sheared off part of an adjacent fan blade.
After the Feb. 20 incident, Pratt & Whitney called for inspections every 1,000 flights, followed by a Federal Aviation Administration order that they be inspected for cracks before their next flight.
Get Boston local news, weather forecasts, lifestyle and entertainment stories to your inbox. Sign up for NBC Boston’s newsletters.
The particular Pratt & Whitney engines involved are found on fewer than 100 Boeing 777 jets currently in use. They're also on several dozen other planes that have been parked because of weak passenger traffic during the pandemic. The affected planes are all used by United Airlines and by carriers in Japan and South Korea.
The engine failure occurred four minutes after the Boeing 777 took off, bound for Hawaii. Debris from the engine and its housing rained down on suburban neighborhoods. The NTSB said the pilots had just increased power to the two engines when a loud bang was captured on the cockpit voice recorder.
Information from the plane's data recorder indicates that the engine shut down automatically and triggered a fire warning. The United pilots declared an emergency and returned to Denver International Airport with one working engine and landed safely. No injuries were reported on the plane or on the ground.
U.S. & World
This story has been updated to correct that the engine failure over Denver occurred Feb. 20, not Feb. 22.