MKC68D0113

NTSB accident investigation · Cessna 150 · Savage, MN · June 12, 1967

Accident · No injuriesClosed
Date
June 12, 1967
Place
Savage, MN · SAVAGE, MN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3464JCessna 150
Status
Completed · report November 9, 1967
Report
Brief approved by the director
Case key
118510

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-2798  67/6/12    SAVAGE,MINN         CESSNA 150          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 20, 69 TOTAL
        TIME - 0805                    N3464J              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 29 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - ROUGH/UNEVEN

Aircraft

Registration
N3464J
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.