UNK65X0339

NTSB accident investigation · Cessna 170B · Jasper, AL · October 19, 1964

Accident · No injuriesClosed
Date
October 19, 1964
Place
Jasper, AL · JASPER, AL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3032ACessna 170B
Status
Completed · report December 2, 1964
Report
Brief approved by the director
Case key
186031

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-3264  64/10/19   JASPER ALA          CESSNA 170B         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 29, 75 TOTAL
        TIME - 1245                    N3032A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 20 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - WALKER COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N3032A
Reported as
Cessna 170B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Walker County

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.