FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA274 · Cessna 172

23 Jun 2012 · Veneta, OR, United States

Cessna 172 · Accident: loss of lift during initial climb

From Crow-Mag Airport (33OR) to Crow-Mag Airport (33OR)

Report a problem

Event

NTSB case
WPR12FA274
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
4 · 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

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
N5781A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Crow-Mag Airport (33OR), Veneta, ORTo Crow-Mag Airport (33OR), Veneta, OR
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
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 › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Witnesses located at their residences adjacent to the accident site reported hearing the airplane takeoff from the airport and that the engine sounded normal. Shortly after, the sound of the engine stopped. One witness reported that while he was outside his home, he saw the accident airplane fly over 100-foot tall trees north of his position at an altitude of about 200 feet above ground level (agl) and that the engine sounded normal. The witness said that while he directed his attention away from the airplane momentarily, he heard the engine suddenly stop and he immediately looked back and observed the airplane descend into 100-foot tall trees.

An iPhone was located within the wreckage and contained a 23-second video recording inside the accident airplane. Review of the video revealed that it began as the airplane initiated takeoff roll on the grass runway. The video briefly captured the engine tachometer gauge, which displayed 2,300 revolutions per minute (RPM). Throughout the video, the engine sound was consistent and did not increase or decrease. During the final 8 seconds of the video, after the airplane became airborne, a sound, similar to a stall warning horn was heard until the end of the recording.

Postaccident examination of the airframe and engine run revealed no evidence of any preimpact mechanical malfunction or failure that would have preluced normal operation. Cockpit documentation revealed that the throttle was in the fully extended or idle position, and was bent downwards. Given the idle position of the throttle and downward bend, it is likely that the pilot reduced power prior to impacting trees. The sound of the stall warning horn within the recorded video suggests that the airplane was traveling at a slow airspeed immediately after takeoff and most likely continued in this state throughout the climb. While witnesses reported hearing the engine lose power, it is possible that the witnesses heard the reduction of engine power from a high power setting to an idle power setting prior to impact with trees, thus being similar to a loss of engine power.

Toxicology tests on the pilot were found positive for metabolites of marijuana within the pilot’s blood and lung tissue. Most behavioral and physiological effects return to baseline levels within 3-5 hours after drug use, although some residual effects in specific behaviors have been demonstrated up to 24 hours, such as complex divided attention tasks. Psychomotor impairment can persist after the perceived high has dissipated. In long term users, even after periods of abstinence, selective attention has been shown to be adversely affected with increasing duration of use, and speed of information processing has been shown to be impaired with increasing frequency of use. The exact degree of impairments in cognition, judgment, and motor function were unable to be determined. The pilot’s use of marijuana was likely more than five hours before the accident and may have contributed to his failure to successfully manage this flight.

Probable cause

The pilot’s failure to maintain adequate airspeed and altitude to clear trees during the initial climb after takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA274
Event ID
20120623X90047
Case number
WPR12FA274
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: 034d752a3f0ec7ccfb01b947271efa8a180c5b92cbeefbe036484086e03848f1; retrieved 2026-09-13T22:27:13.848Z.