MIA69F0106

NTSB accident investigation · Alon A-2 · Tampa, FL · August 25, 1968

Accident · No injuriesClosed
Date
August 25, 1968
Place
Tampa, FL · TAMPA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5691FAlon A-2
Status
Completed · report October 17, 1968
Report
Brief approved by the director
Case key
108891

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-2805  68/8/25    TAMPA,FLA           ALON A-2            CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 29, 18 TOTAL
        TIME - 0930                    N5691F              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PETER-O-KNIGHT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5691F
Reported as
Alon A-2
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Peter-O-Knight

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.