LAX67D0434

NTSB accident investigation · Piper PA-22 · Laverne, CA · May 3, 1967

Accident · Minor injuriesClosed
Date
May 3, 1967
Place
Laverne, CA · LAVERNE, CA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1311CPiper PA-22
Status
Completed · report September 8, 1967
Report
Brief approved by the director
Case key
117126

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-1411   67/5/3    LAVERNE,CALIF       PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 37, 12 TOTAL
        TIME - 1055                    N1311C              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BRACKETT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS - VORTEX TURBULENCE
        REMARKS- LANDED BEHIND NAVY CORSAIR.

Aircraft

Registration
N1311C
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Brackett

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.