LAX69D0228

NTSB accident investigation · Alon A-2 · Riverside, CA · January 3, 1969

Accident · No injuriesClosed
Date
January 3, 1969
Place
Riverside, CA · RIVERSIDE, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5698FAlon A-2
Status
Completed · report April 14, 1969
Report
Brief approved by the director
Case key
191507

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-0055   69/1/3    RIVERSIDE,CALIF     ALON A-2            CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 17, 14 TOTAL
        TIME - 1030                    N5698F              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - RIVERSIDE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5698F
Reported as
Alon A-2
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Riverside

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.