WPR10CA392 · Cessna 172P
Ahart Aviation Cessna 172P · Accident: abnormal runway contact during landing
From Livermore Municipal Airport (KLVK) to Reid-Hillview Airport of Santa Clara County (KRHV)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA392
- 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 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
- N64204
- Operator
- Ahart Aviation
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Livermore Municipal Airport (KLVK), Livemore, CATo Reid-Hillview Airport of Santa Clara County (KRHV), San Jose, CA
- 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
- 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
- Abnormal runway contact
- 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 › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that after a cross-country flight, she maneuvered the airplane onto final approach while maintaining about 65 knots. The pilot flared too early and as a result, the airplane stalled and landed hard. The airplane bounced down the runway and the pilot continued to pull back on the control yoke. After the third bounce, the airplane touched down and came to a stop at the end of the runway. As the pilot was taxiing the airplane back to the parking area, she noticed that when the rudder was fully deflected to the right it made a clipping sound. When she exited the airplane, she examined the airplane and observed the propeller tips were bent. Postaccident examination of the airplane by a Federal Aviation Administration inspector revealed that the airplane sustained substantial damage to the firewall and fuselage. The pilot reported no mechanical failures or malfunctions prior to the accident.
Probable cause
The pilot’s improper flare and inadequate recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA392
- Event ID
- 20100809X53916
- Case number
- WPR10CA392
- 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. 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: 4ec89924c54cd5c7ca23b727fde7a8d3699b9b49bad180ca831e1ddc359c328c; retrieved 2026-09-15T14:48:50.477Z.