# Accident 20140117003192A: Cessna 172N, San Jose, CA, January 17, 2014

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 17, 2014, 16:39 local time
- Place: San Jose, CA
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Taxi
- Operating rules: General operating rules (Part 91)
- Location: 37.3364° N, 121.8217° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3364&lon=-121.8217&mi=10
- Aircraft: N737CL, a cancelled registration (https://openairdocs.org/deregistered/N737CL-2018-03-07) (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
- NTSB investigation: [NTSB WPR14LA099](https://openairdocs.org/ntsb/WPR14LA099) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140117003192A

## Narrative

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

ON JANUARY 17TH, 2014 AT 1639 LOCAL TIME AN AIRCRAFT N6570P PA-24-250 LOST ENGINE POWER AFTER ROTATING OFF OF RUNWAY 31R AT REID HILLVIEW (RHV). THE AIRCRAFT EXECUTED A 270 DEGREE TURN BACK TO THE AIRPORT AND CRASHED BETWEEN TAXIWAY ZULU AND YANKEE, SOUTH OF ECHO. N6570P STRUCK N737CL C-172N AS THE AIRCRAFT WAS TAXIING ON ZULU. NO INJURIES REPORTED FROM EITHER AIRCRAFT. THERE WAS SUBSTANTIAL DAMAGE TO BOTH AIRCRAFT.

## Other aircraft in the event

- N6570P, Piper PA-24-250: [Accident 20140117003132A](https://openairdocs.org/incident/20140117003132A)

## 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 WPR14LA099](https://openairdocs.org/ntsb/WPR14LA099), Jan 18, 2014: Cessna 172N (N737CL), San Jose, CA, substantial damage. Probable cause: The pilot’s failure to sump the fuel tanks, which resulted in water contamination, a partial loss of engine power during takeoff, and collision with a taxiing airplane during the subsequent forced…

## Other reports on N737CL (3)

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

- [Incident 19960424011399I](https://openairdocs.org/incident/19960424011399I), Apr 24, 1996: Cessna 172N (N737CL), Torrance, CA, Minor damage. Narrative: on 4/24/96 at 2325Z, Cessna 152, N757CL, nose wheel was broken off at landing. Pilot reported that as soon as the main gear tires made contact a…
- [Incident 19920119004299I](https://openairdocs.org/incident/19920119004299I), Jan 19, 1992: Cessna 172N (N737CL), San Jose, CA, Minor damage. Pilot made a hard landing. Aircraft porpoised. Propeller struck runway.
- [Accident 19790510042959A](https://openairdocs.org/incident/19790510042959A), May 10, 1979: Cessna 172 (N737CL), Murrieta, CA, Substantial damage. On practice soft-field takeoff, wind gust and non-correction allowed airplane to run off runway and nose over.

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.