Accident Mitsubishi MU-2B-60 N246W, Tuesday 29 March 2016
ASN logo
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 29 March 2016
Type:Silhouette image of generic MU2 model; specific model in this crash may look slightly different    
Mitsubishi MU-2B-60
Owner/operator:Marquise Aviation Corp Trustee (owner)
Registration: N246W
MSN: 1552SA
Year of manufacture:1982
Engine model:Airesearch TPE331 SERIES
Fatalities:Fatalities: 7 / Occupants: 7
Other fatalities:0
Aircraft damage: Destroyed
Location:2km SW Îles-de-la-Madeleine Airport -   Canada
Phase: Approach
Nature:Passenger - Non-Scheduled/charter/Air Taxi
Departure airport:Montreal-St. Hubert Airport, QC (YHU/CYHU)
Destination airport:Îles-de-la-Madeleine Airport, QC (YGR/CYGR)
Investigating agency: TSB
Confidence Rating: Accident investigation report completed and information captured
A Mitsubishi Mu-2B-60 aircraft crashed while on approach to Îles-de-la-Madeleine Airport, Quebec, Canada killing former federal Liberal cabinet minister Jean Lapierre, four members of his family and the two pilots.
The wreckage was contained in a 150m x 150m field. The aircraft came to rest approximately 91m from the initial point of impact.
The aircraft was registered in the United States and was in the process of being purchased by the pilot.

On 13 July 2016 TSB stated:
The investigation has found that both the altitude and the speed of the aircraft's approach to CYGR were higher than recommended. On the MU-2 instrument-approach profile, the standard speed prior to the initial approach fix is 150 knots, slowing to a final approach speed of 125 knots past the final approach fix. In this instance, the aircraft's speed prior to the initial approach fix was 240 knots, and past the final approach fix the speed decreased below 175 knots, only 2.7 nm from Runway 07—much later than prescribed. The aircraft landing gear was lowered and approach flaps were selected at this point. Although not required by regulation, the occurrence aircraft was equipped with a lightweight recording system. The recorder will provide information critical to understanding the circumstances and events that led to the departure from controlled flight—information that would not have been available to the investigation if the aircraft had not been equipped with a recording system.

Findings as to causes and contributing factors:
1. The pilot's inability to effectively manage the aircraft's energy condition led to an unstable approach.
2. The pilot "got behind" the aircraft by allowing events to control his actions, and cognitive biases led him to continue the unstable approach.
3. A loss of control occurred when the pilot rapidly added full power at low airspeed while at low altitude, which caused a power-induced upset and resulted in the aircraft rolling sharply to the right and descending rapidly.
4. It is likely that the pilot was not prepared for the resulting power-induced upset and, although he managed to level the wings, the aircraft was too low to recover before striking the ground.
5. The pilot's high workload and reduced time available resulted in a task-saturated condition, which decreased his situational awareness and impaired his decision making.
6. It is unlikely that the pilot's flight skills and procedures were sufficiently practised to ensure his proficiency as the pilot-in-command for single-pilot operation on the MU-2B for the conditions experienced during the occurrence flight.

10 jan 2018: TSB report , see link below

Accident investigation:
Investigating agency: TSB
Report number: A16A0032
Status: Investigation completed
Duration: 1 year and 9 months
Download report: Final report


CADDORS 2016Q0513

Jan 2018 TSB report:


Revision history:

29-Mar-2016 18:58 harro Added
29-Mar-2016 18:59 harro Updated [Aircraft type, Cn, Operator, Departure airport, Source, Embed code, Narrative]
29-Mar-2016 19:00 harro Updated [Aircraft type]
29-Mar-2016 19:03 harro Updated [Narrative]
29-Mar-2016 19:41 Anon. Updated [Total fatalities]
29-Mar-2016 20:19 Louis Updated [Total fatalities]
29-Mar-2016 23:19 Geno Updated [Aircraft type, Cn, Operator, Location, Nature, Source]
30-Mar-2016 05:38 yukonjack Updated [Source]
30-Mar-2016 05:44 Iceman 29 Updated [Embed code]
30-Mar-2016 09:13 Dmitriy Updated [Operator, Source]
30-Mar-2016 09:26 Aerossurance Updated [Time, Operator, Other fatalities, Location, Nature, Source, Narrative]
30-Mar-2016 19:15 Aerossurance Updated [Location, Nature, Source, Narrative]
31-Mar-2016 07:39 Aerossurance Updated [Source]
01-Apr-2016 11:11 Aerossurance Updated [Embed code]
01-Apr-2016 11:18 Aerossurance Updated [Time, Location, Narrative]
01-Apr-2016 17:50 Anon. Updated [Narrative]
13-Jul-2016 13:58 Aerossurance Updated [Source]
13-Jul-2016 14:01 Aerossurance Updated [Narrative]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
10-Jan-2018 16:06 Iceman 29 Updated [Source, Embed code]
10-Jan-2018 16:07 Iceman 29 Updated [Source]
10-Jan-2018 16:23 Iceman 29 Updated [Source, Damage, Narrative]
10-Jan-2018 18:48 Iceman 29 Updated [Embed code]
10-Jan-2018 19:56 harro Updated [Embed code, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314