FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA017 · Piper PA28 161

16 Oct 2016 · Austin, PA, United States

St. Catharines Flying Club Piper PA28 161 · Accident: abrupt maneuver en route

From Richmond International Airport (RIC) to Niagara District Airport (CYSN)

Report a problem

Event

NTSB case
ERA17FA017
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
3 · 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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Piper PA28 161

Aircraft type
Piper PA28
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
C-GYSN
Onboard fatalities
Unknown
Route
From Richmond International Airport (RIC), Richmond, VATo Niagara District Airport (CYSN), St. Catherines
Aircraft age
About 39 years (built 1977)
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
En route · cruise
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
Abrupt maneuver
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The commercial pilot and two student pilot passengers were conducting an instrument flight rules (IFR) flight. The accident airplane was part of a group of several airplanes from the same flying club. About 2 hours 50 minutes after takeoff, the air traffic controller advised the accident pilot of areas of precipitation along the airplane's route of flight; the flight subsequently diverted west for about 6 minutes before re-establishing its northwesterly course.

Review of weather information indicated that the airplane subsequently passed through an area of light-to-heavy rain with severe turbulence, updrafts and downdrafts, and small hail; temperatures at the airplane's cruise altitude were above freezing. The airplane entered a right turn at its cruise altitude; shortly thereafter, the turn rate increased, and the airplane began to rapidly descend. Radar contact was lost, and the airplane was subsequently located in a heavily wooded area. Examination of the airplane revealed no evidence of preimpact failure or malfunction of the airframe, flight controls, or engine. The significant fragmentation of the wreckage was consistent with a high-energy impact following a loss of control.

Although components of the vacuum-operated attitude indicator and directional gyro exhibited rotational scoring, examination of the engine-driven vacuum pump could not determine whether it was operating at impact. The initial right turn, which was about standard rate, was likely the pilot's attempt to fly out of the adverse weather. The subsequent right turn, at greater than standard rate, was likely due to spatial disorientation in adverse instrument conditions and not the result of a vacuum system malfunction.

The weather encountered during the flight was forecast, but the extent to which the pilot had familiarized himself with the weather conditions before the flight could not be determined, because there was no record of the pilot receiving a weather briefing from an official, access-controlled source. Although the pilot had recently completed an instrument proficiency check (IPC), recovery from unusual attitudes was not a requirement of the IPC. None of his instrument flight experience was conducted in actual instrument conditions, and his most recent night flight experience was about 10 months before the accident.

While the pilot was expecting weather avoidance assistance from the pilot of another airplane based on their verbal agreement before departure, the two pilots did not communicate during the accident flight. Given that the accident airplane was not equipped with onboard weather information, it could not be determined why the pilot chose to deviate in the direction that he did, rather than asking the controller for more information regarding the weather or for assistance in deviating around it. If the pilot had requested assistance, the controller likely would have been able to provide him with vectors to avoid the adverse conditions.

Probable cause

The pilot's loss of control while maneuvering in night instrument conditions that included light-to-heavy rain with severe turbulence, updrafts and downdrafts, and hail. Contributing to the accident was the pilot experiencing spatial disorientation, his lack of flight experience in actual instrument conditions, and his failure to request weather avoidance assistance from air traffic control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA017
Event ID
20161017X65629
Case number
ERA17FA017
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, coordinates. 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: b472c10d23bfee0936a47ecd471051ff36fb7988f219adfc9971ec28eff56c00; retrieved 2026-09-14T22:01:20.596Z.