CEN22LA170 · Cessna 172 R
Cessna 172 R · Accident: loss of control on ground during landing
Event
- NTSB case
- CEN22LA170
- 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 R
- 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
- N857CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 24 years (built 1998)
- 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
- Landing
- Defining eventThe 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 on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that she was practicing touch and go landings. She had just added full power to take off when the airplane veered to the left. The student pilot attempted to correct with the application of right rudder; however, she perceived that the rudder was “locked into place” and required full body weight to apply full right rudder. The student pilot lost control of the airplane and exited the side of the runway which resulted in substantial damage to the fuselage. A postaccident examination of the airplane found no obvious malfunctions with the flight controls, although impact damage precluded full rudder deflection. The instructor pilot that witnessed the accident reported that the wind had increased past what was forecast and past the student pilot’s limit. At the time of the accident the student pilot was taking off on runway 17 with wind from 130° at 12 kts, gusting to 18 kts; the crosswind was calculated to be 11 kts.
Probable cause
The student pilot’s failure to maintain direction control during takeoff in gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA170
- Event ID
- 20220408104916
- Case number
- CEN22LA170
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: dffc6e3366fd71771ea29d7036fe081370a0e812f0a14434f26967d54b8c6f8e; retrieved 2026-09-16T15:07:05.315Z.