FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC14FA068 · Ryan NAVION A

24 Aug 2014 · Coldfoot, AK, United States

Ryan NAVION A · Accident: controlled flight into terrain/object (CFIT) while maneuvering

From Bettles Airport (PABT) to Deadhorse Airport (PASC)

Report a problem

Event

NTSB case
ANC14FA068
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Ryan NAVION A

Aircraft type
Ryan NAVION
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N4827K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bettles Airport (PABT), Bettles, AKTo Deadhorse Airport (PASC), Deadhorse, AK
Aircraft age
About 65 years (built 1949)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB 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 airplane reaching the area of the pass, being boxed in by the surrounding terrain, and not having enough energy or performance to climb up and cross over the pass as the terrain at that point was rising faster than the airplane could climb.

Examination of weight and balance information indicated that the pilot had taken off with the airplane loaded over maximum gross weight and that the airplane was near its maximum gross weight when the accident occurred. The pilot's decision to operate the airplane near its maximum gross weight likely contributed to the accident because it reduced the margin of power available for climb.

Review of Federal Aviation Administration (FAA) records revealed that, from 2007 to 2012, the pilot had a history of accidents, incidents, reexaminations, and checkride failures. Despite the pilot's history and concerns voiced by numerous FAA personnel during the certification process, the FAA issued a certificate to the pilot in 2012 to conduct commercial air transportation pursuant to 14 CFR Part 135.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC14FA068
Event ID
20140825X21423
Case number
ANC14FA068
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 8806b3922e5bf29387d8908614da2e56d3cdcb0bb4c9c8db9302f9ecfda1a0b7; retrieved 2026-09-16T01:40:40.562Z.