CHI00LA174 · Piper PA-28-140
Piper PA-28-140 · Accident: loss of control in flight during initial climb
From 01C to H04 · ROLLO, MO
Event
- NTSB case
- CHI00LA174
- 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
Piper PA-28-140
- Aircraft type
- Piper PA-28
- 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
- N98117
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 01CTo H04 · ROLLO, MO
- 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 › Aircraft control, not maintained
- Stall/mush
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airstrip (runway 27) being used for takeoff was bordered by trees on the north and west sides and the winds were from 210 degrees at 15 knots gusting to 20 knots. The pilot stated there was turbulence on takeoff from the left quartering headwind. He reported that at an altitude of 150 to 200 feet above the ground, the right wing "dipped severely down (on knife edge)" and he corrected the attitude, but the airplane started to buffet. In order to avoid going into the wooded area, he banked the airplane to the left to fly over a corn field with a headwind; however, the airplane continued to descend. The pilot reported the airplane descended until it contacted the terrain in the corn field. He stated that just after touch down the nose gear contacted a "large rock" and the airplane spun around prior to coming to rest.
Probable cause
the pilot's failure to maintain control of the airplane which resulted in a stall/mush condition. Factors associated with the accident were the trees and gusty wind conditions which resulted in turbulence on takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA174
- Event ID
- 20001212X21189
- Case number
- CHI00LA174
- 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: b22ad1cfe4a47a28b71a2b802f1bd0b540f9182907f0867073cbe06b2d3fa5e4; retrieved 2026-09-21T20:11:09.737Z.