CHI66F0142

NTSB accident investigation · Luscombe 8F · Milwaukee, WI · June 21, 1965

Accident · No injuriesClosed
Date
June 21, 1965
Place
Milwaukee, WI · MILWAUKEE, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2036KLuscombe 8F
Status
Completed · report September 17, 1965
Report
Brief approved by the director
Case key
177673

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-2190  65/6/21    MILWAUKEE WIS       LUSCOMBE 8F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 55, 1600
        TIME - 1440                    N2036K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 201 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - TIMMERMAN
        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
N2036K
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Timmerman

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.