NYC66D0328

NTSB accident investigation · Beechcraft S35 · Flushing, NY · October 20, 1965

Accident · No injuriesClosed
Date
October 20, 1965
Place
Flushing, NY · FLUSHING, NY
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N5826KBeechcraft S35
Status
Completed · report December 16, 1965
Report
Brief approved by the director
Case key
175299

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-3253  65/10/20   FLUSHING NY         BEECHCRAFT S35      CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 38, 2000
        TIME - 0010                    N5826K              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 500 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LAGUARDIA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           MISCELLANEOUS - PROP/JET/ROTOR BLAST
        FACTOR(S)
           PERSONNEL - TRAFFIC CONTROL PERSONNEL: INADEQUATE SPACING OF AIRCRAFT
        REMARKS- AIRCRAFT WAS TAXIED BEHIND LARGE AIRCRAFT DURING NIGHT OPERATION

Aircraft

Registration
N5826K
Reported as
Beechcraft S35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Laguardia

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.