Probable cause
The pilot's inadequate landing flare, which resulted in a bounced landing and substantial damage to the firewall.
NTSB analysis
According to the pilot, he established a "crab angle to track" the centerline of the runway and maintained about 70 knots on the final leg of the traffic pattern. He pulled the throttle to idle, began to flare the airplane, and the airplane touched down on the main wheels first. It became airborne again, touched down on the runway, and "bounced" a third time. Then, during the landing roll, the pilot was instructed by the air traffic controller to taxi to the ramp area. As the pilot attempted to maneuver the airplane, he realized that the nose landing gear was "rough" to handle. He notified air traffic control that he was having trouble with the landing gear, and the airplane was towed off the runway. During the accident sequence, the airplane incurred substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind reported at the airport around the time of the accident was calm.
Text from the NTSB. Open the NTSB docket for ERA14CA160 for the full record.
Event
- Date
- Mar 8, 2014
- Type
- Accident
- Place
- Charlottesville, Virginia
- Nearest airport
- Charlottesville-Albemarle (CHO)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Cessna 172N
- N-number
- N5423J
- Category
- Airplane
- Year built
- 1980
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.