code

OR

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

Date & Time: Feb 6, 2019 at 1530 LT
Operator:
Registration:
N997MA
Flight Type:
Survivors:
Yes
MSN:
46-36126
YOM:
1997
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On February 6, 2019, about 1530 Pacific standard time, a Piper PA-46-350P airplane, N997MA, collided with terrain while on short final approach to the Aurora State Airport (UAO), Aurora, Oregon. The private pilot and certified flight instructor were seriously injured and the airplane sustained substantial damage throughout. The airplane was registered to and operated by the pilot under the provision of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight that departed about 1430. The pilot reported that the purpose of the flight was to practice commercial pilot maneuvers. After practicing slow flight, chandelles, lazy eights, and eights on pylons with no issue, they returned to the airport. The flight instructor and he talked through how to conduct a practice power-off 180° landing as they entered the traffic pattern. When the airplane was abeam the 1,000 foot runway markings, the pilot reduced the power to idle and started a left turn toward the runway. He stated that he realized the airplane was probably not going to make the runway; he last recalls the airplane turning sharply to the left, as he was pulling on the control yoke, and adding right rudder input.

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

Date & Time: Apr 7, 2017 at 1048 LT
Registration:
N123SB
Survivors:
No
Site:
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: