MKC68F0512

NTSB accident investigation · Cessna 150 · Grand Forks, ND · April 27, 1968

Accident · No injuriesClosed
Date
April 27, 1968
Place
Grand Forks, ND · GRAND FORKS, ND
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8642GCessna 150
Status
Completed · report May 22, 1968
Report
Brief approved by the director
Case key
111277

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-0931  68/4/27    GRAND FORKS,N DAK   CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 20, 58 TOTAL
        TIME - 0940                    N8642G              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GRAND FORKS INTL
        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
N8642G
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Grand Forks Intl

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.