OAK68D0025

NTSB accident investigation · Piper PA-22 · Hayfork, CA · June 24, 1967

Accident · No injuriesClosed
Date
June 24, 1967
Place
Hayfork, CA · HAYFORK, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4815APiper PA-22
Status
Completed · report September 28, 1967
Report
Brief approved by the director
Case key
116239

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-2140  67/6/24    HAYFORK,CALIF       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 27, 118
        TIME - 1730                    N4815A              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 32 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HAYFORK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           PILOT IN COMMAND - FAILED TO USE OR INCORRECTLY USED MISC.EQUIPMENT
           MISCELLANEOUS ACTS,CONDITIONS - INCORRECT TRIM SETTING

Aircraft

Registration
N4815A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hayfork

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.