SEA07CA116 · Cessna 172M
Gorge Winds Aviation Cessna 172M · Accident: on ground/water collision with terrain/water during takeoff
From Astoria Regional Airport (KAST) to Southwest Washington Regional Airport (KKLS)
Event
- NTSB case
- SEA07CA116
- 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 172M
- 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
- N1911V
- Operator
- Gorge Winds Aviation
- Onboard fatalities
- Unknown
- Route
- From Astoria Regional Airport (KAST), Astoria, ORTo Southwest Washington Regional Airport (KKLS), Kelso, WA
- Aircraft age
- Not recorded
- 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
- Takeoff · roll/run
- First occurrenceThe 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
- On ground/water collision with terrain/water
- 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
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the takeoff roll in a 30 degree crosswind of about 12 knots, the aircraft passed on the leeward side of a number of hangars of varying size. As the aircraft passed through the area where the wind was blocked by the individual hangars into areas where the wind was not blocked, the student pilot failed to adequately compensate for the resultant change in wind velocity and direction. As the student pilot continued the takeoff, the aircraft departed the side of the runway, impacted a taxiway exit sign, and entered into an area of wet, soft ground. The student pilot then pulled the power to idle and applied "full brakes." The nose gear then dug into the terrain and ultimately collapsed. There were no anomalies found in the rudder or nose wheel steering systems.
Probable cause
The student pilot's failure to adequately correct for changing wind conditions, leading to a loss of directional control during the takeoff ground roll. Factors include wet, soft terrain along the side of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA116
- Event ID
- 20070525X00641
- Case number
- SEA07CA116
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 29cf1b77102ea3b2127667604ac81da645153aa0e814f37075b725c661b1a9f4; retrieved 2026-09-22T03:51:57.115Z.