UNK65X0224

NTSB accident investigation · Piper PA24 · Garberville, CA · October 10, 1964

Accident · Minor injuriesClosed
Date
October 10, 1964
Place
Garberville, CA · GARBERVILLE, CA
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6060PPiper PA24
Status
Completed · report November 20, 1964
Report
Brief approved by the director
Case key
181460

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-3186  64/10/10   GARBERVILLE CALIF   PIPER PA24          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 58, 200
        TIME - 1515                    N6060P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 106 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GARBERVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N6060P
Reported as
Piper PA24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Garberville

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.