MIA66D0411

NTSB accident investigation · Cessna 310 · Miami, FL · February 3, 1966

Accident · No injuriesClosed
Date
February 3, 1966
Place
Miami, FL · MIAMI, FL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N830LCessna 310
Status
Completed · report February 23, 1966
Report
Brief approved by the director
Case key
173620

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-0053   66/2/3    MIAMI FLA           CESSNA 310          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 2157                    N830L               PX-  0  0  1  PLEASURE/PERSONAL TRANSP  AGE 40, 4800 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            1000 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - MIAMI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        REMARKS- NIGHT OPERATION

Aircraft

Registration
N830L
Reported as
Cessna 310
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Miami

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.