Boeing 747 451 incident near Tokyo, Jp, June 7, 2017
On June 7, 2017 at about 9:50 am local time, a 1990 Boeing 747 451, registered N668US, was involved in an incident during enroute (cruise) near Tokyo. It was flown under scheduled airline rules (Part 121). No one was hurt; 326 people were on board or involved. The weather was conditions the NTSB did not record.
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 7, 2017 · about 9:50 am local time
- Place
- Tokyo, Japan · map
- Type
- Incident
- Injuries
- No one was hurt; 326 people were on board or involved.
- Weather
- conditions the NTSB did not record
- Aircraft
- Boeing 747 451 451, built 1990 · all 747 451s on the register
- Registration
- N668US · no longer on the register · serial 24223
- Damage
- Not recorded
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during enroute (cruise) defining event
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Fatigue/wear/corrosion
The aircraft
- Maximum gross weight: 870,000 lb
- Seats: 403
- Landing gear: fixed
- Engine 1: P&W PW4000 SER (turbofan); 0 hours total
- Engine 2: P&W PW4000 SER (turbofan); 0 hours total
- Engine 3: P&W PW4000 SER (turbofan); 0 hours total
- Engine 4: P&W PW4000 SER (turbofan); 0 hours total
- Operator: Delta Air Lines
The flight
- Departed from: Tokyo
- Destination: KDTW Detroit MI
- Flight plan: IFR
Weather at the time
- Light: not reported
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 13 | |||
| Flight crew | 4 | |||
| Passengers | 309 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on March 25, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Powerplants Group Chairman's Factual Report | PDF, 60 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
