CHI68D0521

NTSB accident investigation · Luscombe 8E · Richmond, IN · December 19, 1967

Accident · No injuriesClosed
Date
December 19, 1967
Place
Richmond, IN · RICHMOND, IN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2632KLuscombe 8E
Status
Completed · report February 2, 1968
Report
Brief approved by the director
Case key
112606

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-4352  67/12/19   RICHMOND,IND        LUSCOMBE 8E         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 50, 96 TOTAL
        TIME - 1700                    N2632K              PX-  0  0  0  TRAINING                  HOURS, 34 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - RICHMOND MUNIC
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2632K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Richmond Munic

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.