MIA72DKJ28

NTSB accident investigation · Cessna 310 · Troy, AL · October 12, 1971

Accident · No injuriesClosed
Date
October 12, 1971
Place
Troy, AL · TROY, AL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8988ZCessna 310
Status
Completed · report June 15, 1972
Report
Brief approved by the director
Case key
164218

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-3995  71/10/12   TROY,ALA            CESSNA 310          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 1600
        TIME - 1658                    N8988Z              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1450 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - TROY
        DEPARTURE POINT             INTENDED DESTINATION
          RUSSELLVILLE,ALA            TROY,ALA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR

Aircraft

Registration
N8988Z
Reported as
Cessna 310
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Troy

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.