UNK64X2895

NTSB accident investigation · Luscombe 8F · Boulder Creek, CO · July 18, 1964

Accident · Minor injuriesClosed
Date
July 18, 1964
Place
Boulder Creek, CO · BOULDER CREEK, CO
Injuries
1 minor
Damage
Destroyed
Phase of flight
Landing
Aircraft
N9933CLuscombe 8F
Status
Completed · report October 15, 1964
Report
Brief approved by the director
Case key
183097

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-2116  64/7/18    BOULDER CREEK COL   LUSCOMBE 8F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 235
        TIME - 1205                    N9933C              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 45 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BOULDER CREEK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N9933C
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Boulder Creek

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.