MIA67F0438

NTSB accident investigation · Cessna 172 · Opa Locka, FL · March 13, 1967

Accident · No injuriesClosed
Date
March 13, 1967
Place
Opa Locka, FL · OPA LOCKA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3618LCessna 172
Status
Completed · report August 18, 1967
Report
Brief approved by the director
Case key
118122

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-0789  67/3/13    OPA LOCKA,FLA       CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 18, 86 TOTAL
        TIME - 1148                    N3618L              PX-  0  0  0  PRACTICE                  HOURS, 4 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OPA LOCKA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS

Aircraft

Registration
N3618L
Reported as
Cessna 172
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.