ERA22LA177 · Cessna 170 UNDESIGNAT
Cessna 170 UNDESIGNAT · Accident: collision during takeoff/landing on approach
From Gryder-Teague Airport (NC58) to an unrecorded destination
Event
- NTSB case
- ERA22LA177
- 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
- Event fatalities
- Unknown
- 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 170 UNDESIGNAT
- Aircraft type
- Cessna 170
- 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
- N2656V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gryder-Teague Airport (NC58), Taylorsville, NCTo not recorded
- Aircraft age
- About 74 years (built 1948)
- 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
- Approach · VFR go-around
- 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft systems
- 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 airplane owner, who was a student pilot, reported that the pilot-rated passenger was the pilot flying. During landing, the airplane bounced and the owner took control of the airplane and initiated a go-around. He stated that the airplane was slow to climb with the flaps fully extended and they cleared the first tree line but impacted another tree farther away from the airstrip. The owner reported he did not recall anything after the tree contact but did say that there was nothing mechanically wrong with the airframe or engine. The airplane came to rest upright among small diameter trees in a nose-low, tail high attitude with the right wing substantially damaged.
Probable cause
The pilot’s failure to retract the flaps during a go-around from a bounced landing, which resulted in a collision with trees then terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA177
- Event ID
- 20220404104877
- Case number
- ERA22LA177
- 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, cause areas. 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: db9c6cd1548483e84c101062c5bd072bad5fd6f4d601524869b507dcc5ff713d; retrieved 2026-09-16T15:05:45.085Z.