Incident Ryan Navion A N4827K,
ASN logo
ASN Wikibase Occurrence # 169148
 
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:Sunday 24 August 2014
Time:13:05
Type:Silhouette image of generic NAVI model; specific model in this crash may look slightly different    
Ryan Navion A
Owner/operator:Private
Registration: N4827K
MSN: NAV-4-1827
Year of manufacture:1949
Total airframe hrs:4027 hours
Engine model:Continental E225-4
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Location:Atigun Pass, AK -   United States of America
Phase: En route
Nature:Passenger - Non-Scheduled/charter/Air Taxi
Departure airport:Bettles, AK (PABT)
Destination airport:Deadhorse, AK (PASC)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The commercial pilot was conducting a 14 Code of Federal Regulations (CFR) Part 135 commercial air tour flight with three passengers onboard when the airplane impacted rising terrain below the entrance of a high mountain pass. The airplane was substantially damaged, and the pilot and his three passengers were seriously injured. Thirty-five days later, one of the passengers died as a result of his injuries. The pilot initially reported to first responders that he had encountered a severe downdraft while approaching the high mountain pass, which caused the airplane to lose altitude. Review of reported weather conditions at the time of the accident in the area of the pass indicated that the wind speed was 4 to 7 knots, and no indications of sudden downdrafts were discovered.
When interviewed by investigators about 2 weeks after the accident, the pilot stated that the right front seat passenger was not wearing his shoulder harness and had slumped onto the flight controls and become unresponsive after taking a motion sickness drug. The pilot further stated that the two rear seat passengers (who had also taken the drug) were also unresponsive when this occurred. However, none of the three passengers recalled this, and the front seat passenger was found with his seatbelt and shoulder harness on when first responders arrived on scene.
In a written statement dated about 2 months after his interview, the pilot stated that a propeller blade had separated in flight, as one propeller blade was missing and not recovered from the accident site. The passengers did not recall that this had occurred, and postaccident examination of the propeller hub, propeller blade pilot tubes, propeller blade clamps, and the remaining propeller blade indicated that the missing propeller blade had separated during the impact sequence. Evidence that the missing propeller blade separated on impact included the existence of power signatures on the remaining propeller blade and the presence of a large amount of grease in the hub, which was not thrown out in a centrifugal pattern from the missing propeller blade side of the hub as it would have been if the blade had separated in flight. Further findings indicating that the missing propeller blade separated on impact were a broken clamp bolt head found lying inside the clamp bolt cup of the clamp from the missing propeller blade, impact damage on that same clamp, and a shiny-crescent shaped contact mark on the hub butt in the aft quadrant where the trailing edge of the missing propeller blade would have been located; the crescent-shaped contact mark, which was indicative of aluminum transfer from the missing blade to the hub butt, is typically seen when propeller blades separate during impact. Additionally, metallurgical testing showed that the impact-damaged clamp from the missing propeller blade as well as both of the propeller blade tubes had failed due to overload, and no evidence of fatigue cracking was found.
Postaccident examination of the airframe and engine found no evidence of preimpact mechanical malfunctions or anomalies that would have precluded normal operation of the airplane. Several discrepancies were noted with the engine, including the presence of metallic particulates within the oil filter, contamination of the fuel inlet screen with a rubber-like material, and damage to the oil pump consistent with hard particle passage; however, none of these discrepancies would have prevented the engine from producing power.
Witness statements, passenger statements, photographs taken during the flight by one of the passengers, and GPS data recovered from a GPS receiver onboard the airplane indicated that, after takeoff, the pilot did not climb to a safe cruising altitude to cross through the mountain pass but instead remained at low altitude. After circling a town, he proceeded up a valley that led to the high mountain pass, flying below the tops of the surrounding mountains in close proximity to terrain and obstructions about 500 feet above ground level. This low altitude flying resulted in the air
Probable Cause: The pilot’s improper inflight planning and improper decision to deliberately operate the airplane at low altitude in close proximity to obstructions and rising terrain. Contributing to the accident were the pilot’s improper preflight planning and the Federal Aviation Administration’s inappropriate decision to issue a 14 Code of Federal Regulations Part 135 certificate to the operator despite the pilot’s history of accidents, incidents, reexaminations, and checkride failures.

The pilot was later convicted of lying to deferal investigators

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ANC14FA068
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
https://www.adn.com/alaska-news/aviation/2019/11/27/fairbanks-pilot-in-fatal-2014-crash-convicted-of-lying-to-federal-investigators/
https://www.adn.com/alaska-news/aviation/2019/11/27/fairbanks-pilot-in-fatal-2014-crash-convicted-of-lying-to-federal-investigators/

Location

Media:

Revision history:

Date/timeContributorUpdates
24-Aug-2014 23:59 Aerossurance Added
25-Aug-2014 07:07 Aerossurance Updated [Source, Narrative]
25-Aug-2014 09:03 gerard57 Updated [Operator, Total fatalities, Total occupants, Other fatalities, Phase, Nature, Damage, Narrative]
25-Aug-2014 17:56 harro Updated [Aircraft type, Registration, Cn]
25-Aug-2014 21:26 Aerossurance Updated [Operator, Nature, Departure airport, Destination airport, Source, Narrative]
26-Aug-2014 06:52 Aerossurance Updated [Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
16-Mar-2017 13:50 PiperOnslaught Updated [Departure airport, Destination airport, Source, Narrative]
19-Aug-2017 13:57 ASN Update Bot Updated [Time, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]
28-Nov-2019 05:06 Aerossurance Updated [Source]
19-Sep-2020 14:49 Aerossurance Updated [Source, Embed code, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org