FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA12IA114 · Boeing 787 8

28 Jul 2012 · Charleston, SC, United States

Boeing 787 8 · Incident: powerplant system/component malfunction/failure while taxiing

From Charleston International Airport (KCHS) to Charleston International Airport (KCHS)

Report a problem

Event

NTSB case
DCA12IA114
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing 787 8

Aircraft type
Boeing 787
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
VT-ANJ
Onboard fatalities
Unknown
Route
From Charleston International Airport (KCHS), Charleston, SCTo Charleston International Airport (KCHS), Charleston, SC
Aircraft age
Not recorded
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 91: General Aviation
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
Taxi
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
Powerplant system/component malfunction/failure
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a taxi test with no intention for flight, as the airplane was approaching 40 knots speed and prior to the engine N1 accelerating beyond 70%, the right engine N1 began to rollback and an EICAS advisory message was displayed indicating an N2 (high pressure rotor speed) exceedance. The flight crew reduced engine power to idle thrust, concluded the taxi test, and shut down the right engine during taxi back to the ramp. Examination of the right engine revealed extensive damage to the low pressure turbine (LPT).

The fan mid shaft (FMS) retaining nut was still connected to the FMS threads but the forward part of the FMS, from the rear of the forward threads, was separated from the remainder of the FMS. Separation of the rotating LPT section from the fan, allowed the LPT section to translate rearward resulting in extensive secondary engine damage.

Examination confirmed separation of the FMS adjacent to the lock nut face located at the aft most full thread root. The fracture exhibited features indicative of multiple failure modes: one progressive, and one instantaneous. About 85 percent of the fracture surface exhibited features consistent with progressive fracture. The remaining fracture surface showed signs consistent with instantaneous failure by overstress. Further examination revealed features consistent with environmentally assisted cracking (EAC) specific to GE 1014 ultrahigh strength steel.

The FMS threads and the retaining nut were coated with a dry film lubricant, and grease or engine oil was used as an assembly aid. Although a lead based dry film lubricant was previously used on GE engine fan mid shafts, during development of the GEnx engine, the design was changed to incorporate a lead free dry film lubricant, and graphite grease instead of the previously used engine oil as an assembly aid.

Testing of specimens taken from the FMS, and comparison to other dry film lubricants used previously on GE 1014 ultrahigh strength steel indicated that the dry film lubricant used on the incident FMS absorbed moisture at a higher rate. Additionally, the combination of dry film lubricant and graphite assembly grease was shown to increase the corrosion rate of GE 1014.

Following the FMS separation that occurred during this taxi test, GE developed an ultrasonic inspection to scan the forward end of the FMS in the area of the threads where the fracture occurred. While conducting the inspections, a GEnx-1B engine installed on another airplane was found to have an indication of a similar crack on the FMS. This airplane had not yet been operated in flight. Follow up testing indicated the crack exhibited features consistent with progressive environmentally assisted cracking.

Probable cause

The separation of the fan mid shaft resulted from environmentally assisted cracking under static load.

Contributing to the incident was the combination of dry film lubricant applied to the fan mid-shaft and graphite grease used during assembly which made the fan mid-shaft susceptible to corrosion from trapped moisture, and the failure of the engine manufacturer to identify this vulnerability during design/development.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA12IA114
Event ID
20120728X22222
Case number
DCA12IA114
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, coordinates. 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: e80d19a62d6defcc067e123ee5ad337fa35dc7fb5b0e9ddea9d323d8c6e8bbdb; retrieved 2026-09-15T19:06:42.736Z.