UNK64X1352

NTSB accident investigation · Cessna 172 · Woodstock, CT · April 17, 1964

Accident · No injuriesClosed
Date
April 17, 1964
Place
Woodstock, CT · WOODSTOCK, CT
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7660XCessna 172
Status
Completed · report September 11, 1964
Report
Brief approved by the director
Case key
184313

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-0960  64/4/17    WOODSTOCK CONN      CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 37, 2693
        TIME - 1700                    N7660X              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 200 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - WOODSTOCK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- AIRPORT UNDER CONSTRUCTION

Aircraft

Registration
N7660X
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Woodstock

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.