Boeing 747 451 N668US
7 June 2017 · Tokyo, Japan · No injuries
Summary
On 7 June 2017 at about 09:50 local time, a Boeing 747 451 registered N668US, operated by Delta Air Lines, was involved in an incident near Tokyo, Japan. 326 people were on board and nobody was injured. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 09:50
- Classification
- Incident
- Location
- Tokyo, Japan
- Coordinates
- 35.7719, 140.3928
- Aircraft
- Boeing 747 451
- Registration
- N668US
- Category
- Airplane
- Year built
- 1990
- Engines
- 4
- Operator
- Delta Air Lines
- Operating rule
- Part 121: Air Carrier
- Phase of flight
- Not recorded
- Route
- Tokyo → Detroit
- Aircraft damage
- Not recorded
- Weather
- Unk
- Light
- Not Reported
- NTSB number
- ENG17IA026
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 326 | 0 | 0 | 0 | 326 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Boeing 747 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Aug 2017 | Boeing 747 | Frankfurt, Germany | - | Unknown | - |
| 15 Jul 2017 | Boeing 747-87UF | Narita, Japan | Atlas Air | Unknown | - |
| 11 Nov 2017 | Boeing 747 | Maastricht, Netherlands | - | Unknown | - |
| 16 Jan 2017 | Boeing 747 | Bishkek, Kyrgyzstan | - | Fatal | 4 |
| 30 Mar 2017 | Boeing 747 | Glasgow, United Kingdom | - | Unknown | - |
| 26 Aug 2017 | Boeing 747 | Delhi, India | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 5 Mar 2017 | Bell 412 | Matsumoto, Japan | - | Fatal | 9 |
| 23 Sep 2017 | Boeing 777 | Osaka, Japan | KLM | No injuries | - |
| 14 Aug 2017 | Socata TBM 700 | Zemyo, Japan | - | Fatal | 2 |
| 3 Jun 2017 | Cessna 172 | Tateyama, Japan | - | Fatal | 4 |
| 1 Jul 2017 | Boeing 787-9 | Fukushima, Japan | - | Serious injuries | - |
| 22 Oct 2017 | Boeing 737 | Tokyo, Japan | - | Serious injuries | - |