Piper PA 46-310P N123SB
7 April 2017 · Harrisburg, Oregon, United States · Fatal
Summary
On 7 April 2017 at about 17:48 local time, a Piper PA 46-310P registered N123SB was involved in an accident near Harrisburg, Oregon, United States. 4 people were on board and 4 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 17:48
- Classification
- Accident
- Location
- Harrisburg, Oregon, United States
- Coordinates
- 44.2925, -123.1822
- Aircraft
- Piper PA 46-310P
- Registration
- N123SB
- Category
- Airplane
- Year built
- 1984
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Van Nuys → Eugene
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Day
- NTSB number
- WPR17FA085
People
4 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 4 | 4 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The commercial pilot and three passengers departed on an instrument flight rules cross-country 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.
Quoted verbatim from the NTSB record.
Other Piper PA-46 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 May 2017 | Piper PA 46-350P | Nyíregyháza, Hungary | - | No injuries | - |
| 30 Jul 2017 | Piper PA 46 350P | Tahlequah, Oklahoma, United States | - | Minor injuries | - |
| 30 May 2018 | Piper PA 46 | Prescott, Arizona, United States | 1ST Avenue Malibu Services LLC | No injuries | - |
| 19 Jan 2016 | Piper PA 46 | Ottawa, Kansas, United States | NO Boundaries Aviation LLC | Minor injuries | - |
| 29 Dec 2016 | Piper PA 46 | Nashville, Tennessee, United States | Cambusmoon Inc | No injuries | - |
| 7 Sep 2016 | Piper PA 46-310P | Chariton, Iowa, United States | - | Fatal | 1 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 20 Jun 2017 | Van's RV-12 | Eugene, Oregon, United States | Lane Community College | No injuries | - |
| 14 Jun 2017 | Cessna A188 | Salem, Oregon, United States | Industrial Aviation Services Inc | No injuries | - |
| 24 Jun 2017 | Piper PA 22 | Pendleton, Oregon, United States | - | No injuries | - |
| 17 Sep 2017 | Rudberg Todd W VANS ACFT RV8 | Manzanita, Oregon, United States | - | No injuries | - |
| 25 Jun 2017 | Cessna 172 | Roseburg, Oregon, United States | - | No injuries | - |
| 12 Mar 2017 | Cessna 172 | Hillsboro, Oregon, United States | Twin Oaks Airpark Inc | No injuries | - |