MIA68D0316

NTSB accident investigation · Cessna 150F · Opa Locka, FL · October 29, 1967

Accident · No injuriesClosed
Date
October 29, 1967
Place
Opa Locka, FL · OPA LOCKA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8793GCessna 150F
Status
Completed · report January 8, 1968
Report
Brief approved by the director
Case key
113321

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-3838  67/10/29   OPA LOCKA,FLA       CESSNA 150F         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 51, 19 TOTAL
        TIME - 1025                    N8793G              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OPA LOCKA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8793G
Reported as
Cessna 150F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Opa Locka

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.