CHI96LA040 · Cessna 172G
Cessna 172G · Accident: loss of control in flight during initial climb
From 1Y6 to Iowa City Municipal Airport (IOW)
Event
- NTSB case
- CHI96LA040
- 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 172G
- 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
- N6094R
- Operator
- Bell, Douglas M. · private individual
- Onboard fatalities
- Unknown
- Route
- From 1Y6To Iowa City Municipal Airport (IOW), Iowa City, IA
- 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
- Initial climb
- 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/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 › Airspeed, not maintained
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT WINDS WERE FROM 360 DEGREES AT 10 KNOTS. AT FIRST, HE DECIDED TO TAKE OFF TO THE WEST, BUT LATER DECIDED TO TAKEOFF TO THE EAST. NEAR THE EAST END OF THE RUNWAY, THERE WAS A 30 FOOT HIGH POWERLINE AND BUILDING TO THE NORTH. THE AIRPLANE CLEARED THE POWERLINE, BUT THE AIRSPEED CONTINUED TO DECREASE. THE PILOT SAID HE NOTED A FAINT SOUND OF THE STALL WARNING HORN AS THE LEFT WING DROPPED. THE AIRPLANE WAS BEING OPERATED OVER ITS MAXIMUM ALLOWABLE GROSS TAKEOFF WEIGHT. THE PILOT HAD USED THE SAMPLE WEIGHT THAT WAS REFERENCED IN THE PILOT'S OPERATING HANDBOOK, INSTEAD OF USING THE EQUIPMENT LIST WEIGHT.
Probable cause
the pilot's inadequate preflight planning/preparation, which resulted in loss of airspeed and a stall/mush as he was maneuvering to avoid obstructions off the end of the runway. Factors relating to the accident were: the unfavorable wind condition, high obstructions, and the airplane's excessive gross weight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA040
- Event ID
- 20001207X04834
- Case number
- CHI96LA040
- 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: b12df9805b4c10294233269c0ebc48040b6fbbc7e93777afdd322c6daa81eaf9; retrieved 2026-09-21T22:00:17.150Z.