OAK69D0256

NTSB accident investigation · Piper PA-18 · Yreka, CA · February 2, 1969

Accident · No injuriesClosed
Date
February 2, 1969
Place
Yreka, CA · YREKA, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7665DPiper PA-18
Status
Completed · report May 12, 1969
Report
Brief approved by the director
Case key
191708

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-0331   69/2/2    YREKA,CALIF         PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 950
        TIME - 1630                    N7665D              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 350 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - YREKA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: OBJECT                                    LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
        REMARKS- HIT WIND SOCK.

Aircraft

Registration
N7665D
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Yreka

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.