CHI06CA183 · Cessna 172S
Cessna 172S · Accident: loss of control in flight during takeoff
From LQH · Lancaster, OH to an unrecorded destination
Event
- NTSB case
- CHI06CA183
- 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
- Unknown
- 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 172S
- 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
- N335SP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LQH · Lancaster, OHTo 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
- Takeoff
- 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
- 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 attained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was damaged when it impacted the ground after a touch-and-go landing on a grass runway. The pilot reported that he landed the airplane on the runway and applied power to execute a touch-and-go landing. He stated that he looked down to raise the flaps and when he looked up the airplane was on the left side of the runway. He stated that he was already at full power and believed he had sufficient speed to takeoff. He reported that he pulled back on the yoke and turned to the right. He stated that the airplane then stalled and hit the ground. He reported that he had failed to check his airspeed prior to the attempted takeoff. The nose and right main landing gear were separated from the airplane. The pilot reported that this was only his second landing on a grass runway.
Probable cause
The pilot's failure to attain sufficient airspeed during the takeoff which resulted in the inadvertent stall and collision with the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA183
- Event ID
- 20060814X01162
- Case number
- CHI06CA183
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-07-09.
- API snapshot SHA-256: 431de1abc636846dfd8a241e57c819a713736bc589ba9ba40aeea90804879b14; retrieved 2026-09-22T04:41:19.019Z.