20140117003192A

Accident · Substantial damage

FAA accident report · Cessna 172N · San Jose, CA · January 17, 2014

Date
January 17, 2014 · 16:39 local
Place
San Jose, CA
Phase of flight
Taxi
Operating rules
General operating rules (Part 91)
Collision
Collision on the ground
Damage
Substantial damage
Aircraft
N737CL
NTSB investigation
NTSBWPR14LA099
Reported as
Cessna 172N
Reported engine
Lycoming 0-320 series
People aboard
2
Fatal injuries
0
Other injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.

Other reports on N737CL · 3

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