NYC68A0112

NTSB accident investigation · Beech 95-B55 · Windsor Lock, CT · March 25, 1968

Accident · FatalClosed
Date
March 25, 1968
Place
Windsor Lock, CT · WINDSOR LOCK, CT
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N3030QBeech 95-B55
Status
Completed · report July 31, 1968
Report
Brief approved by the director
Case key
110449

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-1676  68/3/25    WINDSOR LOCK,CONN   BEECH 95-B55        CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 49, 1602
        TIME - 2051                    N3030Q              PX-  0  0  0  PRACTICE                  TOTAL HOURS, 620 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BRADLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           TURBULENCE                                               LANDING: FINAL APPROACH
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - VORTEX TURBULENCE
        REMARKS- WIND 3K TEMP 32 DEG.N3030Q WAS LDG BEHIND A CL-44.

Aircraft

Registration
N3030Q
Reported as
Beech 95-B55
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Bradley

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.