UNK64X0190

NTSB accident investigation · Beechcraft 35 · Chicago, IL · January 8, 1964

Accident · No injuriesClosed
Date
January 8, 1964
Place
Chicago, IL · CHICAGO, IL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3365VBeechcraft 35
Status
Completed
Report
Brief approved by the director
Case key
185466

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-0078   64/1/8    CHICAGO ILL         BEECHCRAFT 35       CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 41, 3300
        TIME - 1500                    N3365V              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 1600 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           LANDING: ROLL
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 LANDING: ROLL
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: NORMAL RETRACTION/EXTENSION ASSEMBLY
        REMARKS- RIGHT GEAR RETRACT ROD PIN 35-590057-3 BUCKLED.

Aircraft

Registration
N3365V
Reported as
Beechcraft 35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.