- Date
- May 17, 1972
- Place
- Reno, NV · RENO, NV
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N17BJCessna 310
- Status
- Completed · report February 12, 1973
- Report
- Brief approved by the director
- Case key
- 166529
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-1705 72/5/17 RENO,NEV CESSNA 310 CR- 0 0 2 MISCELLANEOUS AIRLINE TRANSPORT, AGE TIME - 1405 N17BJ PX- 0 0 0 TEST 57, 26000 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 400 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - RENO STEAD DEPARTURE POINT INTENDED DESTINATION RENO,NEV LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLISION WITH GROUND/WATER: CONTROLLED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS PILOT IN COMMAND - FAILED TO ABORT TAKEOFF PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - IMPROPER EMERGENCY PROCEDURES FACTOR(S) PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT TERRAIN - ROUGH/UNEVEN COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- L ENG QUIT,DIDNT ABORT.RESTART OK.UN RAISE GR.SAME ENG QUIT AGAIN,NOT FEATH.PLT UN MAINTAIN FLT.
Aircraft
- Registration
- N17BJ
- Reported as
- Cessna 310
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Reno Stead
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.