CHI98LA122 · Cessna 172
Cessna 172 · Accident: loss of control in flight during initial climb
Event
- NTSB case
- CHI98LA122
- 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 172
- 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
- N6300E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- 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; Tree(s); Wire, transmission
- 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, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said he began his takeoff at the north end of a farm field with rolling terrain. He said the airplane lifted off after a 1,000-foot ground roll. When the airplane had climbed to a pilot-estimated 150-2oo-feet above the ground the pilot said the airplane the airplane '...started to fall out of the sky... .' The STOL-equipped airplane collided with telephone wires, trees and the ground. The flight instructor-rated passenger confirmed the pilot s version of what occurred. The rear seat passenger said the airplane lost lift when it turned to the left as it approached rising terrain. The passenger said the airplane crashed shortly thereafter. The on-scene investigation revealed no mechanical anomalies with the airplane or powerplant that would prevent normal flight. Tire tracks in the 6 to 8-inch high grass showed a takeoff roll of about 1,500-feet. The path through the tree's that the airplane collided with was 90-degrees to the tire tracks.
Probable cause
The pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent in-flight collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA122
- Event ID
- 20001211X09819
- Case number
- CHI98LA122
- 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: 60205b56d917392e5918f98e14cb08e17bc3786005017ae2b28defb3e3ed9f62; retrieved 2026-09-21T11:34:28.975Z.