FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA406 · Cessna 177 A

31 Jul 2016 · Kalispell, MT, United States Possible conflict

Cessna 177 A · Accident: loss of control in flight during initial climb

From Schafer USFS Airport (8U2) to Glacier Park International Airport (GPI)

Report a problem

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

Event

NTSB case
GAA16CA406
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
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

Cessna 177 A

Aircraft type
Cessna 177
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
N30550
Operator
Unknown
Onboard fatalities
Unknown
Route
From Schafer USFS Airport (8U2), Kalispell, MTTo Glacier Park International Airport (GPI), Kalispell, MT
Aircraft age
About 48 years (built 1968)
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
Initial climb
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that during takeoff from a mountain airstrip, and climbing just above the trees lining the runway, the airplane encountered an "extreme wind shear and an enormous downdraft". The pilot further reported the airplane began to descend at 1500-2000 feet per minute and he decided to land on the remaining runway. Subsequently the airplane touched down hard, bounced, and nosed over. The airplane sustained substantial damage to both wings, fuselage, and empennage.

The pilot reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The airplane's hard landing during an aborted takeoff, following an encounter with a downdraft during takeoff initial climb from a remote mountain airstrip, resulting in an uncontrolled descent, attempt to land on the runway remaining, and subsequent nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA406
Event ID
20160802X45159
Case number
GAA16CA406
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: a67d9c12b0c4568a246500b357298859679d94f7dba39811a633eafebf125479; retrieved 2026-09-16T03:44:26.143Z.