# Accident 20080407838309A: Cessna 172S, San Luis Obisp, CA, April 7, 2008

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 7, 2008, 13:00 local time
- Place: San Luis Obisp, CA
- Airport: San Luis County Regional
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 35.2372° N, 120.6425° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.2372&lon=-120.6425&mi=10
- Aircraft: N65630, a cancelled registration (https://openairdocs.org/deregistered/N65630-2009-10-28) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 65 total, 0 in this make and model, 45 in the last 90 days
- NTSB investigation: [NTSB LAX08CA124](https://openairdocs.org/ntsb/LAX08CA124) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20080407838309A

## Narrative

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

(-23)STUDENT PILOT STATED THAT AIRCRAFT PORPOISED UPON LANDING. STUDENT PILOT STATED SHE TAXIED AIRCRAFT TO PARKING AND TIED IT DOWN BUT HAD NO IDEA THE PROPELLER HAD STRUCK THE SURFACE.

## 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 LAX08CA124](https://openairdocs.org/ntsb/LAX08CA124), Apr 7, 2008: Cessna 172S (N65630), San Luis Obispo, CA, substantial damage. Probable cause: The pilot's inadequate landing flare, resulting in a hard landing. Contributing to the accident was the gusty wind condition.

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.