MIA06FA120 · Mitsubishi MU-2B-60
Flyin Cloud Mitsubishi MU-2B-60 · Accident: airframe, component or system failure during initial climb
From Treasure Coast International Airport (FPR) to City of Murfreesboro Airport (MBT)
Event
- NTSB case
- MIA06FA120
- 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
- 1 · 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
Mitsubishi MU-2B-60
- Aircraft type
- Mitsubishi MU-2
- 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
- N316PR
- Operator
- Flyin Cloud
- Onboard fatalities
- Unknown
- Route
- From Treasure Coast International Airport (FPR), Fort Pierce, FLTo City of Murfreesboro Airport (MBT), Murfreesboro, TN
- 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
- Initial climb
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Emergency procedure, not followed
- Reduction gear assembly › Fatigue
- Turboshaft engine, power output shaft › Disconnected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses stated that they observed the twin-engine airplane roll into a steep right bank and enter a spin at a low altitude (less than 700 feet) during the initial climb. The airplane then descended and impacted terrain about 1.5 miles from the end of the departure runway. Some witnesses reported hearing an unusual engine noise just before the airplane began to roll and spin. Day visual meteorological conditions prevailed.
Examination of the right engine revealed that the ring gear support of the engine/propeller gearbox had fractured in flight due to high cycle fatigue originating from the corner radii of the high-speed pinion cutout. The reason for the fatigue could not be determined. The ring gear support disengaged from the ring gear due to this failure, resulting in a disconnection in power being transferred from the engine power section to the propeller.
In addition to the ability for a pilot to manually feather the propellers, and an automatic feathering feature, the engine (Honeywell TPE-331) design also includes a “Negative Torque Sensing” (NTS) system that would automatically respond to a typical failed engine condition involving a propeller that is driving the coupled engine. Feathering the propeller reduces drag and asymmetric yawing due to the failed engine. All Federal Aviation Administration (FAA) certification evaluations for one-engine inoperative handling qualities for the airplane type were conducted with the NTS system operational. According to the airplane manufacturer, the NTS system was designed to automatically reduce the drag on the affected engine to provide a margin of safety until the pilot is able to shut down the engine with the condition lever.
However, if a drive train disconnect occurs at the ring gear support, the NTS system is inoperable, and the propeller can come out of feather on its own, if the disconnect is followed by a pilot action to retard the power lever on the affected engine. In this scenario, once the fuel flow setting is reduced below the point required to run the power section at 100% (takeoff) rpm, the propeller governor would sense an “underspeed” condition and would attempt to increase engine rpm by unloading the propeller, subsequently driving the propeller out of feather toward the low pitch stop. This flat pitch condition would cause an increase in aerodynamic drag on one side of the airplane, and unanticipated airplane control difficulty could result due to the asymmetry.
The emergency procedure for an in flight power loss, regardless of the cause, published in the Airplane Flight Manual (AFM) required that the power lever for the failed engine be moved forward to the Takeoff position (following the step to immediately shut down the engine by moving the condition lever to the Emergency Stop position). Additionally, a “WARNING” follows this procedure to reiterate that the pilot must “…NOT RETARD FAILED ENGINE POWER LEVER.” The warning also states: “PLACE FAILED ENGINE POWER LEVER TO TAKEOFF POSITION DURING THE FEATHERING OF PROPELLER AND LEAVE THERE FOR REMAINDER OF THE FLIGHT."
Postcrash examination of the wreckage revealed evidence that both condition levers were in the “Takeoff/Land” position. The left engine power lever was in the “Reverse” position, and the right engine power lever was in the “Flight Idle” position.
Based on an analysis of evidence from the wreckage and technical data from the airframe and engine manufacturers, a likely scenario for the accident sequence is as follows: Shortly after takeoff, and after being instructed to change frequencies, the pilot may have perceived a loss of power in the right engine and an associated rise in rpm. The right propeller then went into a feathered position about 3 seconds later. The pilot then reduced the right engine power lever, contrary to the AFM procedure. At this point, the fuel flow decreased, leading to a decrease in power section rpm. The propeller governor then sensed an under-speed condition. As a result, oil was routed to the propeller by the propeller governor, causing the propeller to come out of feather toward a flat pitch (increased drag) position. The pilot may not have been aware that the propeller came out of feather. As a result of the increased drag condition on the right side of the airplane, the airplane yawed and rolled to the right and entered a spin. In an attempt to control the airplane, the pilot reduced power on the opposite (left) engine. However, at this point, the airplane was not at a sufficient altitude to recover.
The investigation revealed that a TPE331 engine gearbox uncoupling event is an unusual engine failure that results in substantially different engine indications to a pilot in comparison to a typical flameout event in which the NTS system in operable.
According to the engine manufacturer, there have been five incidents of similar TPE331 ring gear support cracks during about 29 million engine hours of service history. All of the cracks originated at the high-speed pinion cutout detail. Three of these incidents were shop findings, one incident resulted in an in-flight shutdown at altitude followed by a safe landing, and the other incident was this accident.
The accident pilot reportedly accumulated 11,000 hours of total pilot experience, 2,000 of which were in the same make and model as the accident airplane. About 300 hours were logged within the previous six months of the accident. The pilot received recurrent training the same make and model about 11 months before the accident.
On March 3, 2008, the airplane manufacturer published MU-2 Service News No. 110/00-017, entitled “Power Lever Position Warning for In-flight Engine Failure” which reiterated the warning that the failed engine power lever must not be retarded. In January 2009, the airplane manufacturer also published Service News No.114/00-020, entitled “Engine Failure Modes,” which provided additional detail for pilots regarding an uncoupled gearbox, and again reiterated the AFM procedure and warning. In addition, the engine manufacturer intends to issue a letter to provide a description of the engine symptoms and recommended actions in the event of an uncoupling event, or in the event of an engine failure for any reason.
Probable cause
the pilot’s loss of aircraft control during the initial climb which was precipitated by the sudden loss of thrust and increase in drag from the right engine, and the pilot’s failure to adhere to the published emergency procedures regarding the position of the failed engine power lever. Contributing to the accident was the fatigue failure of the right engine’s ring gear support for undetermined reasons, which rendered the propeller’s automatic drag reducing system inoperative.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA06FA120
- Event ID
- 20060630X00859
- Case number
- MIA06FA120
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 5c34fc8669d2691e6e7ea760de5c8dc22c496f98ca0cecd881902849aa42abd4; retrieved 2026-09-20T17:16:04.100Z.