GAA20CA053 · Zenair CH701
Zenair CH701 · Accident: loss of control in flight during takeoff
From Salem-Willamette Valley Airport/McNary Field (SLE) to Salem-Willamette Valley Airport/McNary Field (SLE)
Event
- NTSB case
- GAA20CA053
- 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
Zenair CH701
- Aircraft type
- Zenair CH701
- 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
- N102PH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Salem-Willamette Valley Airport/McNary Field (SLE), Salem, OR
- Aircraft age
- About 10 years (built 2009)
- 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
- 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, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while taking off, the airplane "suddenly jumped" up about 30 ft with a nose-high attitude and rolled right. He corrected by applying left and forward inputs on the flight controls. The airplane then rolled left. Attempting to level the wings, he reduced power, and the airplane impacted terrain. The pilot further reported that it was his first flight in the experimental, amateur-built airplane and that he should have waited for calm winds before trying a first flight in an unfamiliar airplane. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain lateral control during takeoff, which resulted in impact with terrain. Contributing to the accident was the pilot’s improper decision to make his first flight in an airplane he unfamiliar with before waiting for calm winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA20CA053
- Event ID
- 20191103X05342
- Case number
- GAA20CA053
- 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: 1aa04307d45e23903cea2421648250262824b9252f54186c2961ca7683a27ce6; retrieved 2026-09-16T10:32:42.324Z.