FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW97FA262 · Ryan NAVION B

11 Jul 1997 · GARFIELD, CO, United States

Ryan NAVION B · Accident: loss of control in flight while maneuvering

From Central Nebraska Regional Airport (GRI) to Grand Junction Regional Airport (GJT)

Report a problem

Event

NTSB case
FTW97FA262
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
4 · all aircraft and ground
Ground fatalities
0
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
General aviation
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 B

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
N5401K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Central Nebraska Regional Airport (GRI), Grand Island, NETo Grand Junction Regional Airport (GJT), Grand Junction, CO
Aircraft age
Not recorded
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 91: General Aviation
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 · turn to reverse direction
First occurrenceThe 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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall; Utility pole
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Stall, inadvertent

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

NTSB narrative

Witnesses observed the airplane approaching Monarch Pass at low altitude and airspeed. One witness said the wings were 'wobbling.' The airplane banked left, descended, and struck a power pole before colliding with an abandoned mine building. The airplane burned after impact. Family members said the pilot was an experienced mountain pilot, and had made several trips across Monarch Pass, never flying less than 2,000 feet above the highest obstacle. They said two passengers were visiting the United States for the first time; they surmised the pilot was flying at a low altitude to give them a better view of the landscape.

Probable cause

failure of the pilot to maintain adequate airspeed, during a turn to reverse direction, which resulted in a stall and collision with a pole and a building. High density altiitude was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97FA262
Event ID
20001208X08355
Case number
FTW97FA262
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 8a1e97677125b774ca6f369954081b44dc4513e7f7371c398af06e2d653c2ca6; retrieved 2026-09-20T22:54:10.706Z.