# Accident 20180420003879A: Cessna 172N, San Jose, CA, April 20, 2018

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 20, 2018, 14:00 local time
- Place: San Jose, CA
- Damage: Substantial damage
- Phase of flight: Other, Specify
- Operating rules: Pilot school (Part 141)
- Operator: NZDS
- Location: 37.3361° N, 121.8197° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3361&lon=-121.8197&mi=10
- Aircraft: N23AT, registered now (https://openairdocs.org/aircraft/N23AT) (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: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 310 total, 150 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB GAA18CA232](https://openairdocs.org/ntsb/GAA18CA232) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180420003879A

## Narrative

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

DURING A TOUCH-N-GO LANDING THE STUDENT FAILED TO POSITIVELY CONTROL THE AIRCRAFT ALLOWING IT TO VEER RIGHT TOWARDS THE EDGE OF THE RUNWAY.

THE CFI ALLOWED THE SITUATION TO DEVELOP FOR TOO LONG BEFORE TAKING CONTROL OF THE AIRCRAFT.

THE AIRCRAFT DEPARTED THE RIGHT SIDE OF THE RUNWAY AS IT WAS BECOMING AIRBORN. HOWEVER, THE RIGHT MAIN LANDING GEAR (JUST INBOARD OF THE TIRE) STRUCK A RUNWAY SIGN.  SUBSEQUENTLY, THE SIGN BROKE OFF AND BOUNCED UP INTO THE AIR WHERE IT STRUCK THE AIRCRAFT'S RIGHT HORIZONTAL STABILIZER CAUSING SUBSTANTIAL DAMAGE TO IT AND THE ELEVATOR.

THE FLIGHT INSTRUCTOR THEN FLEW THE AIRCRAFT AROUND THE PATTERN, LANDED AND TAXIED TO PARKING WITHOUT FURTHER INCIDENT.

## 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 GAA18CA232](https://openairdocs.org/ntsb/GAA18CA232), Apr 20, 2018: Cessna 172 (N23AT), San Jose, CA, substantial damage. Probable cause: The student pilot’s failure to maintain the runway heading during the approach to land, and the flight instructor’s delayed remedial action.

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.