FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA526 · Cessna 172 UNDESIGNAT

10 Sept 2017 · Coolin, ID, United States

Cessna 172 UNDESIGNAT · Accident: loss of lift during initial climb

From Cavanaugh Bay Airport (66S) to Felts Field (SFF)

Report a problem

Event

NTSB case
GAA17CA526
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 172 UNDESIGNAT

Aircraft type
Cessna 172
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
N5703A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cavanaugh Bay Airport (66S), Coolin, IDTo Felts Field (SFF), Spokane, WA
Aircraft age
About 61 years (built 1956)
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 lift
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
Tree(s)
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 › Action/decision

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

NTSB narrative

The pilot reported that he completed a normal landing to the south at a grass airstrip near a lake that was surrounded by 75-ft-tall pine trees. He added that he and his passengers ate lunch at the airstrip, and during that time, he noticed "mostly calm" wind with an "occasional gust from the south." The pilot further reported that, due to the runway gradient, he decided to take off downhill to the north because the wind sock was indicating a calm wind.

He reported that, during the soft field takeoff, the takeoff roll was normal, but that, about 100 ft above ground level, he noticed that the "climb had slowed" and the "airspeed was dropping." The pilot lowered the nose, the airplane "descended quickly," and then touched down on the runway with about 30 ft remaining. Subsequently, the airplane overran the runway, crossed a road, and impacted a dumpster and trees.

The fuselage and both wings sustained substantial damage.

The pilot reported that the airplane was 25 lbs under maximum gross weight.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

An automated weather observation station (AWOS) 13 nautical miles from the accident site, reported, about the time of the accident, wind from 240° at 6 knots. A review of four hourly AWOS recordings, south and east of the accident site, around the time of the accident, revealed that the wind was variable from the southwest to west at 5 to 10 knots, gusting 15 to 18 knots. The pilot reported that the takeoff was on runway 33. The calculated density altitude was 3,700 ft. According to the Federal Aviation Administration (FAA) density altitude Koch Chart, the airplane would have likely experienced a 32% decrease in the normal climb rate and a 50% increase in the normal takeoff distance.

The FAA's Pilot's Handbook of Aeronautical Knowledge, FAA-H-8083-25B, contained a section titled, "Effect of Obstructions on Wind," which stated in part:

"Another atmospheric hazard exists that can create problems for pilots. Obstructions on the ground affect the flow of wind and can be an unseen danger. Ground topography and large buildings can break up the flow of the wind and create wind gusts that change rapidly in direction and speed. These obstructions range from man-made structures, like hangars, to large natural obstructions, such as mountains, bluffs, or canyons. It is especially important to be vigilant when flying in or out of airports that have large buildings or natural obstructions located near the runway.

The intensity of the turbulence associated with ground obstructions depends on the size of the obstacle and the primary velocity of the wind. This can affect the takeoff and landing performance of any aircraft and can present a very serious hazard."

It is likely that, during the initial climb in high-density altitude conditions, the airplane encountered a quartering tailwind gust as the airplane climbed above the trees, which resulted in a loss of lift and an inability to gain altitude during the initial climb.

Probable cause

The pilot's decision to take off in high-density altitude and gusting quartering tailwind conditions, which resulted in a loss of lift and an inability to gain altitude during the initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA526
Event ID
20170910X00117
Case number
GAA17CA526
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: 68e6db3d696e20fa63397bed0a534f06b0d9b15d4f86e2a29311fb4658d02739; retrieved 2026-09-16T05:49:03.121Z.