OAK67D0057

NTSB accident investigation · Piper PA-28 · Kneeland, CA · July 21, 1966

Accident · No injuriesClosed
Date
July 21, 1966
Place
Kneeland, CA · KNEELAND, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8868JPiper PA-28
Status
Completed · report September 19, 1966
Report
Brief approved by the director
Case key
122023

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-1977  66/7/21    KNEELAND CALIF      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 125
        TIME - 1330                    N8868J              PX-  0  0  0  PRACTICE                  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - KNEELAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N8868J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Kneeland

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.