UNK64X2150

NTSB accident investigation · Cessna 210 · Porterville, CA · June 6, 1964

Accident · No injuriesClosed
Date
June 6, 1964
Place
Porterville, CA · PORTERVILLE, CA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3920YCessna 210
Status
Completed · report September 30, 1964
Report
Brief approved by the director
Case key
183283

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-1571   64/6/6    PORTERVILLE CALIF   CESSNA 210          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 49, 189
        TIME - 2300                    N3920Y              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 14 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PORTERVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3920Y
Reported as
Cessna 210
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Porterville

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.