UNK64X0443

NTSB accident investigation · Luscombe 8E · Pontiac, SC · February 2, 1964

Accident · No injuriesClosed
Date
February 2, 1964
Place
Pontiac, SC · PONTIAC, SC
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N1815KLuscombe 8E
Status
Completed
Report
Brief approved by the director
Case key
185583

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-0211   64/2/2    PONTIAC SC          LUSCOMBE 8E         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1400                    N1815K              PX-  0  0  0  DUAL                      AGE 47, 3000 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            UNK/NR IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLISION WITH GROUND/WATER: CONTROLLED                  TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT
           DUAL STUDENT - IMPROPER OPERATION OF FLIGHT CONTROLS

Aircraft

Registration
N1815K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.