LAX66F0087

NTSB accident investigation · Beechcraft D-35 · Fallbrook, CA · August 30, 1965

Accident · No injuriesClosed
Date
August 30, 1965
Place
Fallbrook, CA · FALLBROOK, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2094DBeechcraft D-35
Status
Completed · report October 22, 1965
Report
Brief approved by the director
Case key
176046

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-2580  65/8/30    FALLBROOK CALIF     BEECHCRAFT D-35     CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 120
        TIME - 2030                    N2094D              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 85 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FALLBROOK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: AUTOMOBILE                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        REMARKS- NIGHT LANDING UTILIZING AUTOMOBILE HEADLIGHTS FOR LANDING REFERENCE.

Aircraft

Registration
N2094D
Reported as
Beechcraft D-35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fallbrook

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.