CEN23LA292 · Cessna 172R
Cessna 172R · Accident: hard landing
From Patrick Leahy Burlington International Airport (KBTV) to an unrecorded destination
Event
- NTSB case
- CEN23LA292
- 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 172R
- 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
- N64AF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Patrick Leahy Burlington International Airport (KBTV), South Burlington, VTTo not recorded
- Aircraft age
- About 26 years (built 1997)
- 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 · flare/touchdown
- 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
- Hard landing
- 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 › Task environment
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the flight instructor, the student pilot was a little high on the final approach for the short field landing, which resulted in a steeper approach. Before touch down, the student decreased the pitch attitude, and there was little to no flare. The airplane landed flat, bounced, then hit the nosewheel first as they touched down and bounced a second time. During the second bounce, both pilots heard a noise, the student felt a vibration in the rudder pedals, and initiated a go-around. The flight instructor assumed control of the airplane during climb out and confirmed there were no anomalies with the rudder system before transferring the controls back to the student. During the next landing, the flight instructor stated that the student flared a little high and the airplane ballooned before touchdown. During the landing roll, the airplane veered to the right and neither pilot was able to maintain directional control. The nose landing gear collapsed as both pilots applied the brakes. The airplane impacted a taxiway light and came to rest on the runway. The airplane sustained substantial damage to the firewall and lower fuselage at the nose landing gear support structure. Based on the pilot’s statements it is likely the nose landing gear was compromised during the first landing attempt. The flight instructor reported that there were no anomalies with the airplane before the first landing. He added that the accident could have been prevented if they had performed a go-around if a stabilized approach was not established.
Probable cause
The student pilot’s improper landing flare, which resulted in a hard, bounced landing and the flight instructor’s delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA292
- Event ID
- 20230710192579
- Case number
- CEN23LA292
- 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: b3db32ffe86d37287f39497fb4df0df693832015b084d85d0cc2f36c09a802c5; retrieved 2026-09-16T17:50:05.643Z.