UNK64X3301

NTSB accident investigation · Luscombe 8E · Colo Springs, CO · August 9, 1964

Accident · No injuriesClosed
Date
August 9, 1964
Place
Colo Springs, CO · COLO SPRINGS, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N2944KLuscombe 8E
Status
Completed · report October 30, 1964
Report
Brief approved by the director
Case key
182384

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-2415   64/8/9    COLO SPRINGS COLO   LUSCOMBE 8E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 1373
        TIME - 0935                    N2944K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1360 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PETERSON FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS

Aircraft

Registration
N2944K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Peterson Field

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.