CEN22LA043 · Cessna 172P
Cessna 172P · Accident: loss of control in flight during landing
Event
- NTSB case
- CEN22LA043
- 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
- Event fatalities
- Unknown
- 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 172P
- 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
- N99715
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 36 years (built 1985)
- 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 in flight
- 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
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he was flying a solo traffic pattern flight when during the final approach to land and configured with 20° of flaps, the airplane began drifting left of the runway centerline. The student pilot applied power to extend the touchdown point while trying to reestablish the airplane over the runway centerline when the airplane “dropped suddenly” onto the runway and began to porpoise. Before the student pilot could recover, the airplane “dropped heavily” a second time, resulting in the nose wheel separating and the airplane departing the left side of the runway. The airplane came to rest on the lower fuselage in the grass. The airplane sustained substantial damage to the forward and bottom fuselage. The student pilot reported there were no preimpact mechanical malfunctions or failures with the airframe and engine that would have precluded normal operation.
The student pilot reported that while in the traffic pattern, the air traffic controller tried to reach him three times with no response. When the student pilot did respond, the controller admonished the student pilot for not paying attention to the radio calls. The student pilot reported that he likely flared too high over the runway and that the admonishment from the controller was “unsettling” and that he should have executed a go-around rather than attempt to land on that approach.
Probable cause
The student pilot’s improper landing flare, which resulted in a hard landing. Contributing was the student pilot’s self-induced pressure to land after being admonished by the controller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA043
- Event ID
- 20211122104286
- Case number
- CEN22LA043
- 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, coordinates, 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: 1609b7806db54cf31699483ac333426e08fa4d8c98468a133a0a31b420dd2179; retrieved 2026-09-16T14:46:31.156Z.