# Accident 20100808042159A: Cessna 172P, San Jose, CA, August 8, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 8, 2010, 12:00 local time
- Place: San Jose, CA
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.3264° N, 121.8186° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3264&lon=-121.8186&mi=10
- Aircraft: N64204, a cancelled registration (https://openairdocs.org/deregistered/N64204-2019-06-12) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 284 total, 10 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB WPR10CA392](https://openairdocs.org/ntsb/WPR10CA392) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100808042159A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

WHILE LANDING AT REID HILLVIEW AIRPORT RUNWAY 13L  THE PILOT EXPERIENCED A HARD LANDING RESULTING  IN THREE TO FOUR BOUNCES. DUE TO THE HARD LANDING THE AIRCRAFT DEVELOPED DAMAGE TO FIREWALL AND COCKPIT FLOOR BOARDS. THE PROPELLER STRUCK THE RUNWAY AND WAS CRITICALLY DAMAGED .

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR10CA392](https://openairdocs.org/ntsb/WPR10CA392), Aug 8, 2010: Cessna 172P (N64204), San Jose, CA, substantial damage. Probable cause: The pilot’s improper flare and inadequate recovery from a bounced landing.

## Other reports on N64204 (3)

Matched to the same aircraft by N-number and date.

- [Accident 20180120001019A](https://openairdocs.org/incident/20180120001019A), Jan 20, 2018: Cessna 172P (N64204), Cloverdale, CA, Substantial damage. A Cessna 172P N64204 took off from santa rosa, CA. Airport and pilot was flying to Cloverdale airport for a solo training mission/full stop landings. With…
- [Incident 20130218002449I](https://openairdocs.org/incident/20130218002449I), Feb 18, 2013: Cessna 172P (N64204), Hayward, CA, Minor damage. PIC stated he was practicing some pattern work. Upon landing hard his aircraft flared and a strong head wind shifted the aircraft to the side of the runway.…
- [Accident 20090420006849A](https://openairdocs.org/incident/20090420006849A), Apr 20, 2009: Cessna 172P (N64204), Livermore, CA, Substantial damage. (-23) On 04/20/2009, at 08:30 PDT at the Livermore (lvk) airport, during approach to the Livermore airport on runway 25R, the pilot was traveling about 70 to…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.