UNK64X3085

NTSB accident investigation · Luscombe 11A · Indianapolis, IN · July 28, 1964

Accident · No injuriesClosed
Date
July 28, 1964
Place
Indianapolis, IN · INDIANAPOLIS, IN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1666BLuscombe 11A
Status
Completed · report October 19, 1964
Report
Brief approved by the director
Case key
182205

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-2246  64/7/28    INDIANAPOLIS IND    LUSCOMBE 11A        CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 0900                    N1666B              PX-  0  0  0  DUAL                      AGE 48, 2500 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            45 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - BOB SHANK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - SPONTANEOUS-IMPROPER ACTION
           DUAL STUDENT - IMPROPER OPERATION OF FLIGHT CONTROLS

Aircraft

Registration
N1666B
Reported as
Luscombe 11A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bob Shank

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.