UNK64X2140

NTSB accident investigation · Cessna 170 · Montevideo, MN · June 6, 1964

Accident · No injuriesClosed
Date
June 6, 1964
Place
Montevideo, MN · MONTEVIDEO, MN
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2601VCessna 170
Status
Completed · report September 29, 1964
Report
Brief approved by the director
Case key
183272

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-1561   64/6/6    MONTEVIDEO MINN     CESSNA 170          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 250
        TIME - 1700                    N2601V              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 190 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MONTEVIDO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2601V
Reported as
Cessna 170
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Montevido

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.