code

MN

Crash of a Piper PA-46-500TP Malibu Meridian in Lake Elmo

Date & Time: Oct 2, 2020 at 1512 LT
Registration:
N62ZM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lake Elmo - Mesquite
MSN:
46-97087
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3828
Captain / Total hours on type:
42.00
Aircraft flight hours:
2850
Circumstances:
On October 2, 2020, about 1512 central daylight time (CDT), a Piper PA-46-500TP, N62ZM, was substantially damaged when it was involved in an accident near Lake Elmo, Minnesota. The airline transport pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The pilot reported that shortly after takeoff from runway 32 at the Lake Elmo airport (21D) and following landing gear retraction, he noticed a “hiccup” in the engine power and immediately started a turn back towards the airport. During the turn, all engine power was lost and the pilot executed a forced landing into a field of standing corn. The airplane impacted the terrain, bounced, and came to rest upright in the corn about ½ mile northwest of the departure end of runway 32. The airplane sustained substantial damage to the right wing as a result of the impact and post-crash fire. The airplane was equipped with a Pratt & Whitney PT6A turboprop engine.
Probable cause:
A total loss of engine power for reasons that could not be determined.
Final Report:

Crash of a Beechcraft 200 Super King Air in Moorhead

Date & Time: Nov 23, 2016 at 1759 LT
Registration:
N80RT
Survivors:
Yes
Schedule:
Baudette - Moorhead
MSN:
BB-370
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5630
Captain / Total hours on type:
89.00
Circumstances:
The commercial pilot was conducting an on-demand passenger flight at night in instrument meteorological conditions that were at/near straight-in approach minimums for the runway. The pilot flew the approach as a non precision LNAV approach, and he reported that the approach was stabilized and that he did not notice anything unusual. A few seconds after leveling the airplane at the missed approach altitude, he saw the runway end lights, the strobe lights, and the precision approach path indicator. He then disconnected the autopilot and took his hand off the throttles to turn on the landing lights. However, before he could turn on the landing lights, the runway became obscured by clouds. The pilot immediately decided to conduct a missed approach and applied engine power, but the airplane subsequently impacted terrain short of the runway in a nose-up level attitude. The pilot reported that there were no mechanical anomalies with the airplane that would have precluded normal operation. It is likely the pilot lost sight of the runway due to the visibility being at/near the straight-in approach minimums and that the airplane got too low for a missed approach, which resulted in controlled flight into terrain. A passenger stated that he and the pilot were not wearing available shoulder harnesses. The passenger said that he was not informed that the airplane was equipped with shoulder harnesses or told how to adjust the seats. The pilot sustained injuries to his face in the accident.
Probable cause:
The pilot's failure to attain a positive climb rate during an attempted missed approach in night instrument meteorological conditions that were at/near approach minimums, which resulted in controlled flight into terrain.
Final Report: