UNK64X2833

NTSB accident investigation · Piper PA-28 · Reno, NV · July 14, 1964

Accident · FatalClosed
Date
July 14, 1964
Place
Reno, NV · RENO, NV
Injuries
3 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N5493WPiper PA-28
Status
Completed · report October 26, 1964
Report
Brief approved by the director
Case key
183647

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
----------------------------------------------------------------------------------------------------------------------------
2-0447  64/7/14  NR.RENO NEVADA        PIPER PA-28         CR-  1  0  0  COMMERCIAL                COMMERCIAL, AGE 40, 1950
        TIME - 0205                    N5493W              PX-  2  0  0  AIR TAXI-PASSG            TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING
        MISSING AIRCRAFT - LATER RECOVERED
        REMARKS- RECOVERY DATE 7/25/64. PILOT DEVIATED FROM DIRECT COURSE BUT NOT LOST OVER MOUNTAINOUS TERRAIN.

Aircraft

Registration
N5493W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.