DEN66D0186

NTSB accident investigation · Beechcraft S35 · Phoenix, AZ · December 4, 1965

Accident · No injuriesClosed
Date
December 4, 1965
Place
Phoenix, AZ · PHOENIX, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8944MBeechcraft S35
Status
Completed · report January 27, 1966
Report
Brief approved by the director
Case key
174819

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-3587   65/12/4   PHOENIX ARIZ        BEECHCRAFT S35      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 44, 530
        TIME - 1745                    N8944M              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 69 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DEER VALLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           SYSTEMS - ELECTRICAL SYSTEM: OTHER
           MISCELLANEOUS ACTS,CONDITIONS - IMPROPER EMERGENCY PROCEDURES
        REMARKS- ELECTRICAL SYSTEM FAILED FOR UNDETERMINED REASON PILOT FAILED TO EXTEND GEAR WITH MANUAL SYSTEM

Aircraft

Registration
N8944M
Reported as
Beechcraft S35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Deer Valley

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.