FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA029 · Bellanca 7GCAA

25 Nov 2016 · Glamis, CA, United States

Bellanca 7GCAA · Accident: loss of control in flight on approach

From Glamis, CA to Glamis, CA

Report a problem

Event

NTSB case
WPR17FA029
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
1 · 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
Visual Meteorological Cond

Bellanca 7GCAA

Aircraft type
Bellanca 7
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
N88373
Operator
Unknown
Onboard fatalities
Unknown
Route
From Glamis, CATo Glamis, CA
Aircraft age
About 42 years (built 1974)
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
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
Loss of control in flight
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
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot was giving a ride to the passenger and was relocating the airplane to a nearby private airstrip for overnight parking. Witnesses located near the airstrip observed the airplane touch down about midfield on the southwest runway while traveling at a high rate of speed. According to the witnesses, the wind was from the east-northeast at 15 to 20 miles per hour, which was a downwind condition for the landing. The pilot performed a go-around, and the airplane pitched upward and banked steeply to the right. The pilot executed a 180° turn to parallel the runway and leveled off at an altitude of about 100 to 150 ft above ground level. Shortly thereafter, the airplane entered a steep right turn toward the runway, and the witnesses lost sight of it.

Examination of the accident site indicated that the airplane impacted terrain in a near vertical attitude about 600 ft short of the approach end of the dirt runway. Postaccident examination of the airplane revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation. The witness observations of the pilot's steep turns and the airplane's near-vertical impact with terrain are consistent with the pilot failing to maintain adequate airspeed while maneuvering aggressively in the traffic pattern, resulting in the airplane exceeding its critical angle of attack and an aerodynamic stall.

The pilot's autopsy results revealed that he had coronary artery disease without evidence of an old or new heart attack. Although this condition placed the pilot at increased risk for a cardiovascular event, there was no evidence that the pilot's coronary artery disease impaired the pilot or contributed to the accident as he was actively maneuvering the airplane up until the stall. Toxicology tests revealed that the pilot had therapeutic levels of the antidepressant sertraline in has blood at the time of the accident. However, sertraline is not known to cause impairment, and it is unlikely that the effects of sertraline impaired the pilot. In addition, the tests revealed that the pilot had a blood level of the antidepressant trazodone well below therapeutic levels, making it unlikely that the effects of trazadone impaired the pilot.

Review of the pilot's personal medical records revealed that he had major depression that was not adequately controlled. This condition is associated with significant cognitive degradation, particularly in executive functioning. Cognitive degradation may not improve even with treatment and remission of the depressed episode, and patients with severe disease are more significantly affected than those with fewer symptoms or episodes.

Although the pilot likely had the skill and experience necessary to safely conduct the flight, he demonstrated poor decision-making and executive function when he decided to attempt a landing with a significant tailwind and elected to maneuver aggressively in the traffic pattern while attempting to perform a go-around and a subsequent landing attempt. It is likely that the pilot's inadequately controlled depression impaired his decision-making and contributed to the accident.

Probable cause

The pilot's improper decision to attempt a downwind landing and his failure to maintain adequate airspeed while maneuvering during a go-around and subsequent landing attempt, which resulted in exceedance of the airplane's critical angle of attack and an aerodynamic stall. Contributing to the accident was the pilot's inadequately controlled depression, which impaired his decision-making.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA029
Event ID
20161125X72838
Case number
WPR17FA029
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: d18246e9c5b607a88aac85680b33ebdc707434010613ac6f78e976bae0e313b3; retrieved 2026-09-14T22:02:48.053Z.