Dual engine shutdown and loss of control during descent

2 fatalities • South Bend, United States of America • Landing (descent or approach)

An aircraft experienced a dual engine shutdown during descent after an unqualified passenger manipulated the engine controls, leading to a fatal crash in a residential area.

What happened

During the cruise phase of flight, a pilot-rated passenger who was not qualified to act as pilot was operating the aircraft controls and engine throttles under the supervision of the private pilot. After receiving clearance to descend to 3,000 feet mean sea level, the pilot instructed the passenger to reduce power to maintain a specific airspeed. During this process, the passenger moved the throttles past the flight idle stops into the fuel cutoff position, causing both engines to shut down. Radar data indicated the aircraft was descending through 6,700 feet mean sea level, approximately 18 miles southwest of the destination, when the loss of power occurred. The pilot declared an emergency and requested vectors to the destination airport.

As the flight approached the airport, an attempt was made to restart the engines. While the cockpit voice recorder did not capture a successful restart, the pilot's ability to execute a go-around during the first approach suggests at least one engine was operational. During the second approach, witnesses noted that only the nose landing gear had been deployed. The aircraft bounced several times on the runway before entering a nose-low, rolling descent into a nearby residential neighborhood. The accident resulted in fatalities and significant impact damage.

Findings

Post-accident investigations found no mechanical failures that would have prevented the aircraft from operating normally. The investigation determined that the pilot's decision to allow an unqualified passenger to manipulate the engine controls caused the dual engine shutdown. Furthermore, the pilot failed to properly follow emergency procedures. Although the pilot attempted to restart an engine, the battery toggle switch remained in the standby position, preventing the Essential Bus from receiving power. This electrical limitation likely prevented the full extension of the main landing gear. While the landing gear alternate extension handle was partially pulled, the pilot failed to fully extend it, which would have allowed for a successful single-engine landing.

Probable cause

The pilot's decision to permit an unqualified passenger to manipulate engine controls led to a dual engine shutdown, compounded by a failure to follow emergency procedures for electrical and landing gear deployment.

Frequently asked questions

What happened in the 2013-03-17 Raytheon 390 Premier I accident near South Bend, United States of America?

An aircraft experienced a dual engine shutdown during descent after an unqualified passenger manipulated the engine controls, leading to a fatal crash in a residential area.

Were there any fatalities in the 2013-03-17 Raytheon 390 Premier I accident?

The accident was fatal, resulting in 2 fatalities.

What aircraft was involved and where did it happen?

The accident on 2013-03-17 involved a Raytheon 390 Premier I, registration N26DK, operated by Digicut Systems, at South Bend, United States of America.

What was the probable cause of the accident?

The pilot's decision to permit an unqualified passenger to manipulate engine controls led to a dual engine shutdown, compounded by a failure to follow emergency procedures for electrical and landing gear deployment.

Loading the flight search…