Crash of a Piper PA-46-350P Malibu Mirage off Mainau Island: 2 killed

Date & Time: Aug 8, 2017 at 1152 LT
Operator:
Registration:
HB-PPH
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Zurich – Hamburg
MSN:
46-36045
YOM:
1996
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2236
Aircraft flight hours:
2408
Circumstances:
The single engine airplane departed Zurich Airport Runway 28 at 1134LT bound for Hamburg-Helmut Schmidt Airport, carrying one passenger and one pilot. After passing over the city of Konstanz at an altitude of 16,750 feet in IFR conditions, the airplane entered an uncontrolled descent and eventually crashed in the Konstanz Lake, about 200 metres off Mainau Island. The wreckage was found at a depth of 60 metres and both occupants were killed.
Probable cause:
Loss of control while cruising in IMC conditions with strong atmospheric turbulences associated with icing conditions.
Final Report:

Crash of a Piper PA-46-310P Malibu in Harrisburg: 4 killed

Date & Time: Apr 7, 2017 at 1048 LT
Registration:
N123SB
Flight Type:
Survivors:
No
Schedule:
Van Nuys – Eugene
MSN:
46-8508023
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
5060
Captain / Total hours on type:
163.00
Aircraft flight hours:
3681
Circumstances:
The commercial pilot and three passengers departed on an instrument flight rules crosscountry flight. While on approach to the destination airport, the pilot indicated to the air traffic controller that the airplane was passing through areas of moderate-to-extreme precipitation. After clearing the airplane for the approach, the controller noted that the airplane descended below its assigned altitude; the controller issued a low altitude alert, but no response was received from the pilot. The airplane subsequently impacted terrain in a level attitude about 12 miles from the airport. Examination of the airframe, engine, and system components revealed no evidence of preimpact mechanical malfunction that would have precluded normal operation. An area of disturbed, flattened, tall grass was located about 450 ft southwest of the accident site. Based on the images of the grass, the National Weather Service estimated that it would take greater than 35 knots of wind to lay over tall grass as the images indicated, and that a downburst/microburst event could not be ruled out. A downburst is an intense downdraft that creates strong, often damaging winds. About 6 hours before the flight, the pilot obtained weather information through a mobile application. Review of weather data indicated the presence of strong winds, heavy precipitation, turbulence, and low-level wind shear (LLWS) in the area at the time of arrival, which was reflected in the information the pilot received. Given the weather conditions, it is likely that the airplane encountered an intense downdraft, or downburst, which would have resulted in a sudden, major change in wind velocity. The airplane was on approach for landing at the time and was particularly susceptible to this hazardous condition given its lower altitude and slower airspeed. The downburst likely exceeded the climb performance capabilities of the airplane and resulted in a subsequent descent into terrain. It is unknown if the accident pilot checked or received additional weather information before or during the accident flight. While the flight was en route, several PIREPs were issued for the area of the accident site, which also indicated the potential of LLWS near the destination airport; however, the controller did not provide this information to the pilot, nor did he solicit PIREP information from the pilot. Based on published Federal Aviation Administration guidance for controllers and the widespread adverse weather conditions in the vicinity of the accident site, the controller should have both solicited PIREP information from the pilot and disseminated information from previous PIREPs to him; this would have provided the pilot with more complete information about the conditions to expect during the approach and landing at the destination.
Probable cause:
An encounter with a downburst during an instrument approach, which resulted in a loss of control at low altitude. Contributing to the accident was the air traffic controller's failure to
solicit and disseminate pilot reports from arriving and departing aircraft in order to provide pilots with current and useful weather information near the airport.
Final Report:

Crash of a Piper PA-46-310P Malibu in Chichén Itzá

Date & Time: Feb 15, 2017 at 2000 LT
Operator:
Registration:
N116TH
Flight Type:
Survivors:
Yes
Schedule:
Monterrey – Cancún
MSN:
46-8608005
YOM:
1986
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While overflying the Yucatán Province, en route from Monterrey to Cancún, the pilot informed ATC that he was low of fuel and requested the permission to divert to Chichén Itzá Airport for an emergency landing. While approaching the airfield by night, the single engine aircraft descended into trees and crashed few km from the airport. The airplane was destroyed and there was no fire. All five occupants were injured.

Crash of a Piper PA-46-350P Malibu Mirage in Nashville

Date & Time: Dec 29, 2016 at 1345 LT
Operator:
Registration:
N301BK
Flight Type:
Survivors:
Yes
Schedule:
Memphis – Nashville
MSN:
46-36407
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1550
Captain / Total hours on type:
1092.00
Aircraft flight hours:
1332
Circumstances:
According to the pilot, during the landing roll, the airplane "began to drift sharply to the left." The pilot reported that, although there were no wind gusts reported, he felt as though a wind gust was pushing the airplane to the left. He attempted to maintain directional control with rudder pedal application, and he applied full right aileron. The airplane continued to drift to the left, and the pilot attempted to abort the landing by applying full throttle and 25° of flaps. He reported that the airplane continued to drift to the left and that he was not able to achieve sufficient airspeed to rotate. The airplane exited the runway, the pilot pulled the throttle to idle, and he applied the brakes to avoid obstacles. However, the airplane impacted the runway and taxiway signage and came to rest in a drainage culvert. The airplane sustained substantial damage to both wings. The published METAR for the accident airport reported that the wind was from 290° at 15 knots, and wind gusts exceeded 22 knots 1 hour before and 1 hour after the accident. The pilot landed the airplane on runway 20. The maximum demonstrated crosswind component for the airplane was 17 knots. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's loss of directional control during the aborted landing in gusting crosswind conditions, which resulted in a runway excursion.
Final Report: