UNK64X1762

NTSB accident investigation · Luscombe 8E · Brinkley, AR · May 14, 1964

Accident · No injuriesClosed
Date
May 14, 1964
Place
Brinkley, AR · BRINKLEY, AR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2124KLuscombe 8E
Status
Completed · report September 21, 1964
Report
Brief approved by the director
Case key
183938

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-1275  64/5/14    BRINKLEY ARK        LUSCOMBE 8E         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1900                    N2124K              PX-  0  0  0  DUAL                      AGE 24, 2300 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            25 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - BRINKLEY MUNICIPL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           DUAL STUDENT - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS

Aircraft

Registration
N2124K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Brinkley Municipl

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.