UNK65X0585

NTSB accident investigation · Cessna 170B · Wabasso, MN · November 6, 1964

Accident · FatalClosed
Date
November 6, 1964
Place
Wabasso, MN · WABASSO, MN
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8355ACessna 170B
Status
Completed · report February 2, 1965
Report
Brief approved by the director
Case key
181790

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
----------------------------------------------------------------------------------------------------------------------------
2-0812   64/11/6 NR.WABASSO MINN       CESSNA 170B         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 23, 224
        TIME - 2000                    N8355A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 155 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LAMPRECHT FARM
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: TRAFFIC PATTERN-CIRCLING
           COLLISION WITH GROUND/WATER: UNCONTROLLED                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED ALTITUDE
        REMARKS- ELEVATORS JAMMED FROM IMPACT WITH TREES-DARK UNLIGHTER TERRAIN

Aircraft

Registration
N8355A
Reported as
Cessna 170B
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Lamprecht Farm

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.