LAX68F0003

NTSB accident investigation · Luscombe 8F · Chino, CA · June 5, 1967

Accident · Minor injuriesClosed
Date
June 5, 1967
Place
Chino, CA · CHINO, CA
Injuries
1 minor
Damage
Destroyed
Phase of flight
Approach
Aircraft
N2137BLuscombe 8F
Status
Completed · report September 22, 1967
Report
Brief approved by the director
Case key
116669

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-1906   67/6/5    CHINO,CALIF         LUSCOMBE 8F         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 26, 67 TOTAL
        TIME - 2025                    N2137B              PX-  0  0  0  TRAINING                  HOURS, 58 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CHINO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: TRAFFIC PATTERN-CIRCLING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
           MISCELLANEOUS ACTS,CONDITIONS - POORLY PLANNED APPROACH
        REMARKS- ACFT STRUCK TREE ON BASE LEG.NO DUAL NIGHT INSTRUCTION.LDG LIGHTS NOT USED.ACFT STAYED IN TREE.

Aircraft

Registration
N2137B
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Chino

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.