St. Lucie County International Airport
Aircraft Accident/Incident Report

Fort Pierce, Florida 34982
Sunday, June 25, 2006 12:24 EDT

NTSB Narrative Summary Released at Completion of Accident

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.

NTSB Probable Cause Narrative

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.

Event Information

Type of Event Accident
Event Date 6/25/2006
Event Day of the Week Sunday
Time of Event 1224
Event Time Zone Eastern Daylight Time
Event City Fort Pierce
Event State FLORIDA
Event Country --
Zipcode of the event site 34982
Event Date Year 2006
Event Date Month 6
MidAir Collision Indicator No
On Ground Collision occurred ? No
Event Location Latitude 272825N
Event Location Longitude 0802012W
Event Location Airport St. Lucie County International
Event Location Nearest Airport ID FPR
Indicates whether the acc/inc occurred off or on an airport Off Airport/Airstrip
Distance from airport in statute miles 2
Degrees magnetic from airport --
Airport Elevation 275
Weather Briefing Completeness --
Investigator's weather source Weather Observation Facility
Time of the weather observation 1225 Eastern Daylight Time
Direction of event from weather observation facility (degrees) 180
Weather Observation Facility ID FPR
Elevation of weather observation facility 21
Distance of event from weather observation facility (units?) 2
Time Zone of the weather observation EDT
Lighting Conditions Day
Lowest Ceiling Height 4100
Lowest Non-Ceiling Height 2700
Sky/Lowest/Cloud Conditions Few
Sky Condition for Lowest Ceiling Broken
Visibility Runway Visual Range (Feet) --
Visibility Runway Visual Value (Statute Miles) --
Visibility (Statute Miles) 10
Air Temperature at event time (in degrees celsius) 29
Dew Point at event time (in degress fahrenheit) 22
Wind Direction (degrees magnetic) 260
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) 5
Wind Velocity Indicator --
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 29.88
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report --
Event Highest Injury Fatal
On Ground, Fatal Injuries --
On Ground, Minor Injuries --
On Ground, Serious Injuries --
Injury Total Fatal 1
Injury Total Minor --
Injury Total None --
Injury Total Serious --
Injury Total All 1
Investigating Agency NTSB
NTSB Docket Number (internal use) 26450
NTSB Notification Source FAA ATL ROC
NTSB Notification Date Jun 25 2006 12:00AM
NTSB Notification Time --
Fiche Number and/or location -used to find docket information --
Date of most recent change to record Dec 22 2009 2:35PM
User who most recently changed record lema
Basic weather conditions Visual Meteorological Cond
FAA District Office Orlando, Florida

Aircraft Involved

Aircraft #1

Aircraft Registration Number N316PR
NTSB Number MIA06FA120
Missing Aircraft Indicator --
Federal Aviation Reg. Part Part 91: General Aviation
Type of Flight Plan filed IFR
Flight plan Was Activated? Yes
Damage Destroyed
Aircraft Fire Ground
Aircraft Explosion None
Aircraft Manufacturer's Full Name MITSUBISHI
Aircraft Model MU-2B-60
Aircraft Series Identifier --
Aircraft Serial Number 761SA
Certified Max Gross Weight 11575
Aircraft Category Airplane
Aircraft Registration Class --
Aircraft is a homebuilt? No
Flight Crew Seats 2
Cabin Crew Seats --
Passenger Seats 8
Total number of seats on the aircraft 10
Number of Engines 2
Fixed gear or retractable gear Retractable
Aircraft, Type of Last Inspection Conditional
Date of Last Inspection May 13 2006 12:00AM
Airframe hours since last inspection 53
Airframe Hours 4073
ELT Installed Yes
ELT Activated No
ELT Aided Location of Event Site No
ELT Type Unknown
Aircraft Owner Name Flyin Cloud LLC
Aircraft Owner Street Address 1000 2nd Avenue South
Aircraft Owner City North Myrtle Beach
Aircraft Owner State SC
Aircraft Owner Country USA
Aircraft Owner Zipcode 29582
Operator is an individual? No
Operator Name Flyin Cloud LLC
Operator Same as Owner? Yes
Operator Is Doing Business As --
Operator Address Same as Owner? No
Operator Street Address 1000 2nd Avenue South
Operator City North Myrtle beach
Operator State SC
Operator Country USA
Operator Zip code 29582
Operator Code --
Owner has at least one certificate None
Other Operator of large aircraft? No
Certified for Part 133 or 137 Operation --
Operator Certificate Number --
Indicates whether an air carrier operation was scheduled or not --
Indicates Domestic or International Flight --
Operator carrying Pax/Cargo/Mail --
Type of Flying (Per_Bus / Primary) Ferry
Second Pilot on Board No
Departure Point Same as Event Yes
Departure Airport Code FPR
Departure City Fort Pierce
Departure State FL
Departure Country USA
Departure Time 1223
Departure Time Zone EDT
Destination Same as Local Flt --
Destination Airport Code MBT
Destination City Murfreesboro
Destination State TN
Destination Country USA
Specific Phase of Flight Takeoff - initial climb
Report sent to ICAO? --
Evacuation occurred --
Date of most recent change to record Dec 22 2009 2:34PM
User who most recently changed record lema
Since inspection or accident Time of Accident
Event Location Runway Number and Location 14
Runway Length 4756
Runway Width 100
Sight Seeing flight No
Air Medical Flight No
Medical Flight --