MKC66D0311

NTSB accident investigation · Cessna 150 · Rochester, MN · October 14, 1965

Accident · No injuriesClosed
Date
October 14, 1965
Place
Rochester, MN · ROCHESTER, MN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8042SCessna 150
Status
Completed · report February 14, 1966
Report
Brief approved by the director
Case key
175412

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-3748  65/10/14   ROCHESTER MINN      CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 26, 34 TOTAL
        TIME - 1630                    N8042S              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ROCHESTER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: WHEELS,TIRES,AXLES
           MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE
        REMARKS- LEFT MAIN GEAR TIRE FAILED.

Aircraft

Registration
N8042S
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rochester

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.