ASN Wikibase Occurrence # 194611
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: | Friday 7 April 2017 |
| Time: | 10:48 |
| Type: |  Piper PA-46-310P Malibu |
| Owner/operator: | Private |
| Registration: | N123SB |
| MSN: | 46-8508023 |
| Year of manufacture: | 1984 |
| Total airframe hrs: | 3681 hours |
| Engine model: | Continental TSIO-520BE2F |
| Fatalities: | Fatalities: 4 / Occupants: 4 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Harrisburg, OR -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Van Nuys, CA (VNY) |
| Eugene, OR (OG32) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
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.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=123SB
https://flightaware.com/live/flight/N123SB
Location
Images:
Photo: NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 07-Apr-2017 19:43 | gerard57 | Added |
| 07-Apr-2017 19:45 | harro | Updated [Aircraft type, Location, Destination airport, Source] |
| 07-Apr-2017 19:47 | harro | Updated [Time, Aircraft type, Registration, Cn, Operator, Source] |
| 07-Apr-2017 19:49 | harro | Updated [Departure airport, Destination airport] |
| 08-Apr-2017 07:22 | gerard57 | Updated [Date] |
| 08-Apr-2017 09:45 | Iceman 29 | Updated [Source, Embed code, Narrative] |
| 14-Apr-2017 07:24 | Iceman 29 | Updated [Source, Embed code, Narrative] |
| 14-Apr-2017 14:31 | Aerossurance | Updated [Time, Source, Narrative] |
| 22-Aug-2018 10:37 | ASN Update Bot | Updated [Time, Operator, Departure airport, Destination airport, Source, Embed code, Narrative] |
| 22-Aug-2018 11:09 | harro | Updated [Source, Embed code, Narrative, Photo, ] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation