# Accident 20150430006549A: Cessna 172P, Pacoima, CA, April 30, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 30, 2015, 11:34 local time
- Place: Pacoima, CA
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 34.2619° N, 118.4161° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.2619&lon=-118.4161&mi=10
- Aircraft: N65813, registered now (https://openairdocs.org/aircraft/N65813) (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: Student
- Pilot flight hours: 18 total, 18 in this make and model, 18 in the last 90 days
- NTSB investigation: [NTSB GAA15CA063](https://openairdocs.org/ntsb/GAA15CA063) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150430006549A

## Narrative

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

THE ACCIDENT OCCURRED DURING THE STUDENT PILOT?S FIRST SOLO FLIGHT. THE STUDENT FLEW WITH THE FLIGHT INSTRUCTOR FOR ABOUT ONE HOUR THE DAY OF THE ACCIDENT. AFTER AN HOUR OF INSTRUCTION, THE INSTRUCTOR AND THE STUDENT PILOT DID TWO TRAFFIC PATTERNS AT WHITEMAN AIRPORT. THE INSTRUCTOR THEN GOT OUT OF THE AIRPLANE TO LET THE STUDENT SOLO IN THE TRAFFIC PATTERN.

ON THE FIRST LANDING THE AIRCRAFT PORPISED AND BOUNCED SEVERAL TIMES ON THE RUNWAY. THE SECOND LANDING HAD THE SAME RESULTS. THE TOWER AT WHITMAN AIRPORT SUGGESTED FOR THE STUDENT PILOT TO TAXI BACK TO THE HANGER AFTER THE SECOND LANDING. THE DAMAGE WAS NOT DISCOVERED UNTIL MAY 6, 2015.

## 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 GAA15CA063](https://openairdocs.org/ntsb/GAA15CA063), Apr 30, 2015: Cessna 172P (N65813), Los Angeles, CA, substantial damage. Probable cause: The student pilot's failure to maintain attitude control during the landing flare, resulting in a hard landing.

## Other reports on N65813 (2)

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

- [Incident 20190702008839I](https://openairdocs.org/incident/20190702008839I), Jul 2, 2019: Cessna 172P (N65813), Corvallis, OR, Minor damage. Pilot in command lost control of the CE-172 airplane during a planned touch and go maneuver on runway 35 at Corvallis Municipal Airport (kcvo). The airplane…
- [Incident 19861125070219I](https://openairdocs.org/incident/19861125070219I), Nov 25, 1986: Cessna 172P (N65813), Fresno, CA. Deteriorating weather caused VFR pilot to request landing assistance. Pilot not familiar with radio light switch.

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.