LAX67F0274

NTSB accident investigation · Luscombe 8A · Piru, CA · January 13, 1967

Accident · No injuriesClosed
Date
January 13, 1967
Place
Piru, CA · PIRU, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1357BLuscombe 8A
Status
Completed · report June 2, 1967
Report
Brief approved by the director
Case key
119222

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-0121  67/1/13    PIRU,CALIF          LUSCOMBE 8A         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 25, 64 TOTAL
        TIME - 1730                    N1357B              PX-  0  0  0  TRAINING                  HOURS, 16 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SLOAN RANCH STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        REMARKS- STRUCK RAISED CONCRETE CASING.

Aircraft

Registration
N1357B
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sloan Ranch Strip

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.