FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA115 · Ryan NAVION F

26 Feb 2017 · Westhampton Beach, NY, United States

Ryan NAVION F · Accident: aerodynamic stall/spin on approach

From Francis S Gabreski Airport (FOK) to Francis S Gabreski Airport (FOK)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's fatalities. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA17FA115
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
2 · all aircraft and ground Possible conflict
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
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 F

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
N4529K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Francis S Gabreski Airport (FOK), Westhampton Beach, NYTo Francis S Gabreski Airport (FOK), Westhampton Beach, NY
Aircraft age
About 66 years (built 1951)
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
Approach · VFR go-around
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
Aerodynamic stall/spin
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot, who was the owner of the airplane, was receiving a flight review from an instructor who was not familiar with the airplane make and model. The pilot stated that they did not discuss the potential differences between the accident airplane and the airplanes the instructor typically flew before the flight. After departing, they flew to a nearby airport to perform touch-and-go landings. The pilot was performing the first approach for landing in gusty wind conditions. About 100 ft above the runway, the flight instructor took control of the airplane. The airplane landed hard and bounced back into the air. The pilot applied full engine power in an attempt to avoid a stall when the flight instructor yelled, "hands off the yoke." The airplane subsequently experienced an aerodynamic stall/spin and impacted terrain. Postaccident examination of the airframe and engine revealed no anomalies that would have precluded normal operation.

The pilot stated that the design of the accident airplane resulted in a "sight picture" during the landing approach that appeared "very steep." He also stated that, although slipping with the wing flaps fully extended is prohibited in many airplanes, such a maneuver is not prohibited in the accident airplane. The pilot opined that the abnormal sight picture observed during the landing approach and his slipping of the airplane with the flaps extended may have caused the instructor to "[feel] the need to take control of the aircraft at such a critical point in flight."

Federal Aviation Administration Advisory Circular (AC) 61-98D provides information for pilots and flight instructors to use when complying with the requirements of the flight review. The AC states that, before giving a flight review in an unfamiliar aircraft, an instructor should obtain recent flight experience in that aircraft or sufficient knowledge of its limitations, characteristics, and performance.

Although the reason that the instructor took control of the airplane could not be determined, it is likely that he felt the pilot was performing an unsafe maneuver that required intervention; however, it is possible that he interpreted the pilot's actions as unsafe due to his lack of familiarity with the airplane and its operating characteristics. During the subsequent go-around following the bounced landing, the instructor exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall and spin.

Probable cause

The flight instructor's exceedance of the critical angle of attack during a go-around, which resulted in an aerodynamic stall/spin. Contributing to the accident was the flight instructor's failure to familiarize himself with the flight characteristics of the unfamiliar airplane before conducting the flight review.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA115
Event ID
20170226X24343
Case number
ERA17FA115
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: 192afed4cbd56a0f6179ea2edd33b935642a38d18d4657112a3ed8f20ebd2978; retrieved 2026-09-15T05:59:02.275Z.