# N64204: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 1
- Last cancelled: June 12, 2019
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=64204
- Page: https://openairdocs.org/aircraft/N64204

## Aircraft that carried N64204

- [Cancelled 2019-06-12](https://openairdocs.org/deregistered/N64204-2019-06-12): Cessna 172P, S/N 17275534, built 1981. Sale reported, canceled. Owner: [Rantoul, KS](https://openairdocs.org/faa-place/KS/Rantoul)

## NTSB investigations on N64204 (3)

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 WPR18CA072](https://openairdocs.org/ntsb/WPR18CA072), Jan 20, 2018: Cessna 172P (N64204), Cloverdale, CA, substantial damage. Probable cause: The pilot's failure to maintain airplane control during the approach and his delayed decision to go around.
- [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.
- [NTSB WPR09CA209](https://openairdocs.org/ntsb/WPR09CA209), Apr 20, 2009: Cessna 172P (N64204), Livermore, CA, substantial damage. Probable cause: The student pilot’s improper recovery from a bounced landing.

## FAA accident and incident reports on N64204 (4)

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.

- [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 20100808042159A](https://openairdocs.org/incident/20100808042159A), Aug 8, 2010: Cessna 172P (N64204), San Jose, CA, Substantial damage. 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…
- [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…

---
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.