FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Air Lines Flight 158

2 Oct 2015 · Russian airspace, Japan

Boeing 747 451 · Incident: loss of engine power (partial) en route

From Incheon International Airport (RKSI) to Detroit Metropolitan Wayne County Airport (KDTW)

Report a problem

Event

NTSB case
ENG16IA001
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Unknown

Boeing 747 451

Aircraft type
Boeing 747
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N662US
Onboard fatalities
Unknown
Route
From Incheon International Airport (RKSI), SeoulTo Detroit Metropolitan Wayne County Airport (KDTW), Detroit, MI
Aircraft age
About 27 years (built 1988)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft power plant

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

The examination of the engine confirmed that there were three holes in the LPT case. But the holes were under the LPT cooling air manifolds and plenum that did not have any damage. In addition, there was no damage to the inside of the engine's cowlings nor did any debris fall out when the cowlings were opened. There was no damage to the LPT cooling air manifolds and plenum that were over the holes and was there was no debris in the cowlings indicating that no debris passed through the LPT case that made this a contained event rather than uncontained.

The disassembly of the engine revealed one 3rd stage turbine vane cluster, No. 29, was missing although the cluster's bolt hole tab with the retaining nut were still in place on the inner transition duct. The missing cluster's inner shroud was found in the bottom of the engine in the path of the 3rd stage turbine blades. The metallurgical examination of the inner shroud revealed fatigue, however the full extent of the fatigue could not be determined because the end of the fracture surface was smeared.

The examination of the remainder of the LPT revealed all the other turbine vane clusters were complete and in place or the inner and outer shrouds were in place with just the airfoils missing. All the LPT blades were fractured and the fracture surfaces were coarse and grainy indicating an overload fracture. The examination of the remainder of the engine between the fan and high-pressure turbine did not reveal any damage. The extensive damage to the LPT and the absence of damage throughout the remainder of the engine indicated that the damage to the engine originated within the LPT.

The visual examination and a dimensional inspection of the LPT case revealed the 3rd stage turbine vane hooks had extensive wear that varied significantly between adjacent hooks. The dimensional inspection revealed the hook for 3rd stage turbine vane cluster No. 29, the missing vane cluster, had the most wear and that wear was tapered. The tapered wear on the hook and indicates that the vane cluster's outer foot disengaged from the LPT case and tilted rearward. It was not possible to determine the cause of the tapered wear on the LPT case vane hook that led to the vane cluster disengaging. The finding of fatigue on the inner shroud further supports that the vane cluster's outer foot disengaged from the LPT case initially and fatigue was caused by either the transfer of the loads to the inner shroud or from the cluster being strummed by the passing 3rd stage turbine blades.

The review of the engine's maintenance showed that it had last been overhauled in October 2005 and since accumulated 35,545 hours and 3,532 cycles of service. Although the engine was overhauled in October 2005, the LPT module's maintenance records show that it had been swapped from another engine and accumulated 17,441 hours and 2,184 cycles since its previous overhaul. So, at that time of event, the LPT module accumulated 52,986 hours and 6,546 cycles since it had been last overhauled. Except for the low cycle fatigue life limits for specific rotating parts that are outlined in the engine manual, there is no prohibition for an engine or LPT module to have operated as long as this module had been in service. The review of the LPT module's maintenance records from the previous overhaul show that the LPT case modification to the anti-rotation slots had been previously complied with. In addition, the records show that the modification to the 3rd stage turbine vane clusters to remove material from the outer platform gussets had been complied with as well. Because of previous contained and uncontained PW4000 LPT events, P&W has revised the engine manual to add extensive inspections and repairs to LPT components as well as limiting the number of strip and recoat repairs that can be done to PW4000 LPT airfoils. The inspections and repairs that were subsequently adopted into an airworthiness directive (AD) included a visual and dimensional inspection of the LPT case's vane hooks. The tapered wear that was noted on the LPT case's 3rd stage turbine vane hooks occurred over time. The records do not list any work on the LPT case's vane hooks at the last overhaul, so it cannot be determined if the wear that resulted in the disengagement of the 3rd stage turbine vane cluster had existed only from the last overhaul or had existed prior to that overhaul. However, the revised inspection and repair procedures that are now mandated by an AD likely would have captured the wear and required it to be repaired or the case replaced.

Probable cause

The PW4056 engine experienced an in-flight loss of power because of damage to the low-pressure turbine (LPT) because of the inadequate overhaul inspection and repair instructions that existed at the time of the LPT module's last overhaul. A vane hook in the LPT case wore to the point to allow a 3rd stage turbine vane cluster to disengage and eventually fall into the path of the 3rd stage turbine blades causing extensive downstream damage to the LPT module.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG16IA001
Event ID
20151005X35533
Case number
ENG16IA001
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 13273321c9b2e5e820d68ea1010e65c59aee8ecb17b1d493be6de08293e2d3a1; retrieved 2026-09-16T02:51:20.682Z.