CHI96LA234 · Cessna 172L
Cessna 172L · Accident: in flight collision with terrain/water on approach
From Jackson County Airport/Reynolds Field (JXN) to an unrecorded destination
Event
- NTSB case
- CHI96LA234
- 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 172L
- 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
- N7545G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jackson County Airport/Reynolds Field (JXN), Jackson, MITo not recorded
- 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
- In flight collision with terrain/water
- 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/mush
- 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 › Raising of flaps, premature
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, prior to landing, he over flew the runway to check for deer, geese, and sand hill cranes which are 'common around this airport.' During landing, he touched down at approximately 40 miles per hour. As the nose gear touched the runway he saw four sand hill cranes 20 to 30 feet in front of him. He applied full power and pulled back on the yolk. The airplane was 'mushing, nose up, in the air. The pilot was 'retracting the flaps and pushing forward on the yolk to get the nose down.' The airplane impacted the terrain left of the runway on the left main landing gear, then the right main, then the nose gear. The nose gear collapsed and the airplane nosed over sustaining substantial damage.
Probable cause
the pilot's premature raising of the flaps during a go-around. The presence of birds was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA234
- Event ID
- 20001208X06173
- Case number
- CHI96LA234
- 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: investigation status. 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: 6fc76f29af14f8391d250828b9a3aeb7c4f00bc2582a983ff4877d35c8909618; retrieved 2026-09-22T21:55:32.515Z.