FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Mokulele Flight Service Flight 1770

21 Oct 2013 · Wailea, HI, United States Possible conflict

Cessna 208 B · Accident: loss of engine power (total) en route

From Kahului International Airport (OGG) to Waimea Kohala Airport (MUE)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR14FA024
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
Accident
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
Charter & commuter
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

Cessna 208 B

Aircraft type
Cessna 208
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
N861MA
Onboard fatalities
Unknown
Route
From Kahului International Airport (OGG), Kahului, HITo Waimea Kohala Airport (MUE), Waimea-Kohala, HI
Aircraft age
About 13 years (built 2000)
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 135: Air Taxi & Commuter
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 · climb to 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
Substantial

Cause areas

  • Aircraft › Aircraft power plant
  • Personnel issues › Task performance

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

NTSB narrative

According to the flight crew, as the airplane passed through about 8,000 ft mean sea level during climb over open ocean water, they heard a loud bang and a grinding sound, which was followed by a loss of engine power. Sparks were observed coming out of the engine's right exhaust. The flight crew initiated a turn back towards the departure airport, which was about 13 miles north of their position. The crew accomplished the emergency checklists and elected to perform an emergency landing on a highway. During the landing roll, the airplane struck two highway traffic signs, which resulted in substantial damage to the right wing.

A postaccident examination of the airplane's engine revealed that all of the compressor turbine (CT) blades had separated near the blade platforms, and the remaining stubs were gouged and battered. The fracture surface of one of the blades displayed smooth features characteristic of fatigue fracture; all other blade fracture surfaces displayed course features characteristic of overload fracture. The fatigue-fractured blade's microstructure in the fracture area was normal, and the blade material and hardness met engineering drawing requirements. The CT hub displayed a frosted appearance over the entire front and aft surfaces, and glass beads and bead fragments were observed between the fir-tree joints of the blade platforms and the CT disc, consistent with the disc assembly having been cleaned by aggressive glass media blasting in the assembled condition. The engine manufacturer specifies that all media blast cleaning be performed with the CT disc and blades disassembled. The glass bead contamination of the fir-tree joints caused the CT blades to be unevenly restrained, and it altered the blades' designed vibration frequency, making them susceptible to the aerodynamic vibrations from the combustor gas flow. Therefore, the fatigue fracture of the blade was most likely due to the glass bead contamination.

The CT disc assembly had been removed from the engine for repair about two months before the accident, and this was likely when the glass bead media cleaning occurred and the beads became embedded in the exposed fir tree joints. When the CT disc assembly is installed in the engine, the fir tree joints are protected from exposure; therefore, the glass bead contamination could not have occurred when the engine was installed on the airplane.

Probable cause

Improper maintenance that resulted in contamination of the engine's compressor turbine disc and blade assembly by glass bead remnants, which resulted in a blade failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14FA024
Event ID
20131022X24004
Case number
WPR14FA024
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-10-22.
  • API snapshot SHA-256: cb17c8ce0f4590baf4dcd655aeb4d96d3b3f5c6a44755b39a5ebc06e880fbca2; retrieved 2026-09-15T22:59:53.598Z.