LAX68D0063

NTSB accident investigation · Beech 35 · Perris, CA · July 28, 1967

Accident · No injuriesClosed
Date
July 28, 1967
Place
Perris, CA · PERRIS, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2896VBeech 35
Status
Completed · report October 25, 1967
Report
Brief approved by the director
Case key
115704

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-2595  67/7/28    PERRIS,CALIF        BEECH 35            CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 37, 750
        TIME - 1715                    N2896V              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 581 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - KNOX RANCH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2896V
Reported as
Beech 35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Knox Ranch

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.