The U.S. aircraft register, updated daily
Accidents · NTSB MIA06FA120 · Final report

Mitsubishi MU-2B-60 accident near Fort Pierce, Florida, June 25, 2006

On June 25, 2006 at about 4:24 pm local time, a Mitsubishi MU-2B-60, registered N316PR, was destroyed in an accident near Fort Pierce, Florida (St. Lucie County International airport). It was a ferry flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 25, 2006 · about 4:24 pm local time
Place
Fort Pierce, Florida · St. Lucie County International · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Mitsubishi MU-2B-60 · all MU-2B-60s on the register
Registration
N316PR · registry record · serial 761SA
Damage
Destroyed
Flight
Ferry flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 11,000 hours in all; 2,000 in this make and model
  • Last flight review: July 25, 2005
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,073 hours
  • Last inspection: condition inspection, May 13, 2006; 53 hours since
  • Maximum gross weight: 11,575 lb
  • Seats: 10
  • Landing gear: retractable
  • Engine 1: Honeywell TPE-331-10 (turboprop); 0 hours total
  • Engine 2: Honeywell TPE-331-10 (turboprop); 0 hours total
  • Fire on the ground
  • Operator: Flyin Cloud LLC

The flight

  • Departed from: FPR Fort Pierce FL at 4:23 pm
  • Destination: MBT Murfreesboro TN
  • Flight plan: IFR
  • Runway 14, 4,756 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,100 ft; a few clouds at 2,700 ft
  • Temperature: 84°F (29°C), dew point 72°F (22°C)
  • Altimeter: 29.87 inHg
  • Observation at 4:25 pm from FPR, 2 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.