# Incident 20180617008099I: Cessna 172N, Fullerton, CA, June 17, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 17, 2018, 08:20 local time
- Place: Fullerton, CA
- Airport: Fullerton Municipal
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.8719° N, 117.9797° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.8719&lon=-117.9797&mi=10
- Aircraft: N734RS, registered now (https://openairdocs.org/aircraft/N734RS) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 62 total, 62 in this make and model
- NTSB investigation: [NTSB ANC18LA079](https://openairdocs.org/ntsb/ANC18LA079) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180617008099I

## Narrative

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

STUDENT PILOT OPERATED AIRCRAFT ON SOLO FLIGHT WITHOUT SOLO ENDORSEMENT, REQUIRED SIX ATTEMPTS TO LAND AIRCRAFT. ON THE SIXTH, DAMAGED FIREWALL, NOSE GEAR, AND PROPELLER STRUCK THE RUNWAY.

## 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 ANC18LA079](https://openairdocs.org/ntsb/ANC18LA079), Jun 17, 2018: Cessna 172 (N734RS), Fullerton, CA, substantial damage. Probable cause: The National Transportation Safety Board did not determine the probable cause of this event and does not plan to issue a report or open a public docket. The investigation of this event is being…

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.