FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Air Lines Flight 276

7 Jun 2017 · Tokyo, Japan

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

From Tokyo to Detroit Metropolitan Wayne County Airport (KDTW)

Report a problem

Event

NTSB case
ENG17IA026
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
N668US
Onboard fatalities
Unknown
Route
From TokyoTo Detroit Metropolitan Wayne County Airport (KDTW), Detroit, MI
Aircraft age
About 27 years (built 1990)
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 · cruise
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 (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The disassembly and examination of the engine revealed a 5th stage compressor blade was fractured transversely across the airfoil directly above the blade root platform. Unfortunately, that fractured blade was lost during the shipment of the engine parts from Delta Air Lines to P&W's Material and Processes Engineering Laboratory. However, the similarity of the elliptical-shaped fracture surface on that 5th stage compressor blade to the elliptical-shaped fracture surfaces on 6th, 7th, 8th, and 9th compressor blades that were confirmed as fatigue fractures would indicate the 5th stage compressor blade also fractured due to a fatigue crack. The PN 5th stage blade that fractured in this engine and the compressor blade that it had superseded had a combined total of 38 airfoil fractures that would suggest some subtle interrelationship that would cause a resonance leading to a fracture. A detailed examination of the HPC did not identify anything that could have triggered an airflow disturbance. The fractured blade 5th stage compressor blade was subsequently superseded with a new blade in 2011 that has not experienced any fractures suggesting that whatever was causing the fractures was designed out.

The engine's turbine sections sustained extensive thermal and mechanical damage. When the 5th stage compressor blade fractured, the cascade of damage through the HPC disabled the compressor's ability to pump air. The FDR showed that following the loss of power after the 5th stage compressor blade fractured, the fuel flow dropped to zero but then recovered to a sub idle level probably from the electronic control's auto relight feature activating the igniter plugs. Although the fuel flow was less than what was seen when the airplane taxied out for departure, with little to no airflow through the engine, the combustion flame would stagnate around the turbine vanes and blades burning off the early stages and the liberated pieces causing the mechanical damage to the trailing stages.

This incident was initially reported as an uncontained event because of the 360° circumferential split in the LPT case. The examination of the split showed that the edges were not pursed outward indicating there was not a ballistic challenge of liberated blade to the case. The examination of the LPT case showed that the case's walls were not bulged radially outward indicating that there was not a ball up of material whirling around the case. The examination did show that the edges of the cut in the case matched the edges of the circumferential breaks in the 6th stage blade outer airseal segments that both matched the geometry of the 6th stage blade tip shroud indicating that a tip shroud was dragged around by one of the near full length blades as the engine wind milled during the return to NRT. So although the LPT case was cut in half, this was not an uncontained event.

Probable cause

The PW4056 engine lost power due to the fatigue fracture of a 5th stage compressor blade. The cause of the fatigue fracture could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG17IA026
Event ID
20170607X22245
Case number
ENG17IA026
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, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e06c4bdb109a592113a655d66a67436a74a3566dc4f733fd6f03e3c47e02902b; retrieved 2026-09-16T05:22:40.545Z.