LAX65D0043

NTSB accident investigation · Beechcraft B50 · Coso Junction, CA · February 24, 1965

Accident · Minor injuriesClosed
Date
February 24, 1965
Place
Coso Junction, CA · COSO JUNCTION, CA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3568BBeechcraft B50
Status
Completed · report May 18, 1965
Report
Brief approved by the director
Case key
178993

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-0632  65/2/24    COSO JUNCTION CAL   BEECHCRAFT B50      CR-  0  0  1  COMMERCIAL                COMMERCIAL, FL.INSTR.,
        TIME - 0830                    N3568B              PX-  0  0  0  AIR TAXI-PASSG            AGE 41, 11000 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 2000 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - GILL FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS

Aircraft

Registration
N3568B
Reported as
Beechcraft B50
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gill 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.