MIA73FKT03

NTSB accident investigation · Cessna 150D · Opa Locka, FL · July 4, 1972

Accident · No injuriesClosed
Date
July 4, 1972
Place
Opa Locka, FL · OPA LOCKA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5979TCessna 150D
Status
Completed · report March 26, 1973
Report
Brief approved by the director
Case key
167792

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-3777   72/7/4    OPA LOCKA,FLA       CESSNA 150D         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 43, 66 TOTAL
        TIME - 1148                    N5979T              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OPA LOCKA WEST
        DEPARTURE POINT             INTENDED DESTINATION
          OPA LOCKA,FLA               LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N5979T
Reported as
Cessna 150D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Opa Locka West

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.