UNK64X1036

NTSB accident investigation · Cessna 172B · Winona, MN · March 25, 1964

Accident · No injuriesClosed
Date
March 25, 1964
Place
Winona, MN · WINONA, MN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7621TCessna 172B
Status
Completed · report September 4, 1964
Report
Brief approved by the director
Case key
184504

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-0705  64/3/25    WINONA MINN         CESSNA 172B         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 17, 68 TOTAL
        TIME - 1215                    N7621T              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MAX CONRAD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER COMPENSATION FOR WIND CONDITIONS
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND

Aircraft

Registration
N7621T
Reported as
Cessna 172B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Max Conrad

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.