OAK71DVA14

NTSB accident investigation · Cessna 310 · Visalia, CA · August 4, 1970

Accident · No injuriesClosed
Date
August 4, 1970
Place
Visalia, CA · VISALIA, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6946TCessna 310
Status
Completed · report June 11, 1971
Report
Brief approved by the director
Case key
191197

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-3408   70/8/4    VISALIA,CALIF       CESSNA 310          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 35, 490
        TIME - 1405                    N6946T              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 145 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - VISALIA MUNICIPAL
        DEPARTURE POINT             INTENDED DESTINATION
          PORTERVILLE,CALIF           VISALIA,CALIF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        REMARKS- PWR APCH TO LDG.

Aircraft

Registration
N6946T
Reported as
Cessna 310
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Visalia Municipal

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.