UNK64X2714

NTSB accident investigation · Beechcraft G35 · Sacramento, CA · July 8, 1964

Accident · No injuriesClosed
Date
July 8, 1964
Place
Sacramento, CA · SACRAMENTO, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5096BBeechcraft G35
Status
Completed · report October 12, 1964
Report
Brief approved by the director
Case key
182986

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-1989   64/7/8    SACRAMENTO CALIF    BEECHCRAFT G35      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 28, 916
        TIME - 2045                    N5096B              PX-  0  0  2  BUSINESS                  TOTAL HOURS, 146 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SACRAMENTO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        FACTOR(S)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- FAULTY WARNING HORN FLASHER UNIT

Aircraft

Registration
N5096B
Reported as
Beechcraft G35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sacramento

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.