ERA21LA055 · Cessna 172 N
Civil Air Patrol Cessna 172 N · Accident: collision with terrain/object (non-CFIT) on approach
Event
- NTSB case
- ERA21LA055
- 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 172 N
- 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
- N23NJ
- Operator
- Civil Air Patrol
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 41 years (built 1979)
- 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 pattern final
- 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 with terrain/object (non-CFIT)
- 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
As the flight instructor and the private pilot approached the runway for landing, the flight instructor told the pilot the airplane was getting too low and that he needed to add power “more than once.” When the pilot did not add sufficient power to correct the descent, she attempted to add it herself, but it was too late, and the airplane’s left wing stuck the tree. The airplane then struck the ground short of the runway, continued forward until it reached the runway lip, and then nosed over. The airplane’s left wing and the fuselage were substantially damaged. The operator reported there were no preimpact mechanical failures or malfunctions of the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain a proper glidepath while on approach to the runway, and the flight instructor’s delayed remedial action, which resulted in the airplane colliding with a tree on final approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA055
- Event ID
- 20201125102339
- Case number
- ERA21LA055
- 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, 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: 854647cd8fa65bea7f9433beaacee1a5765569de4476d3be8312531c5f6ff448; retrieved 2026-09-16T13:25:57.518Z.