CHI96LA256 · Cessna 172M
Cessna 172M · Accident: loss of control in flight on approach
From Crystal Airport (MIC) to Backus Municipal Airport (7Y3)
Event
- NTSB case
- CHI96LA256
- 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
- 0
- 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
- N1620V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Crystal Airport (MIC), Minneapolis, MNTo Backus Municipal Airport (7Y3)
- 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
- Approach · VFR go-around
- 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
- Loss of control in flight
- 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
- Stall/spin
- 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 › Altitude, not maintained
- Pilot in command › Maneuver to avoid obstructions, abrupt
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that he was above the glidepath on final approach and did not feel comfortable with the situation. He decided to execute a go-around. He advanced the throttle to full power and moved the flap switch up two notches from 40 degrees of flaps to 20 degrees of flaps. 'Everything seemed to be going fine when the next thing I saw was the tree tops.' The pilot 'instinctively pulled back on the yoke' to clear the trees. 'The airplane dipped to the left,' struck the trees and fell to the ground. Examination of the wreckage revealed no anomalies with the airplane.
Probable cause
the pilot's failure to maintain adequate altitude and his abrupt maneuver to avoid the tree tops. The dark night was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA256
- Event ID
- 20001208X06193
- Case number
- CHI96LA256
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-07-27.
- API snapshot SHA-256: 8be38a98916cbd1710e90ddef3ae9a897db5961cc9553aed28a278ce5a888727; retrieved 2026-09-21T21:38:29.267Z.