MKC68D0328

NTSB accident investigation · Cessna 150 · Washington, IA · November 17, 1967

Accident · No injuriesClosed
Date
November 17, 1967
Place
Washington, IA · WASHINGTON, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7799FCessna 150
Status
Completed · report October 17, 1968
Report
Brief approved by the director
Case key
112861

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-4121  67/11/17   WASHINGTON,IOWA     CESSNA 150          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 106
        TIME - 1010                    N7799F              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 83 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - WASHINGTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7799F
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Washington

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.