NYC67D0325

NTSB accident investigation · Cessna 140A · Sutton, WV · October 12, 1966

Accident · No injuriesClosed
Date
October 12, 1966
Place
Sutton, WV · SUTTON, WV
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5619CCessna 140A
Status
Completed · report December 20, 1966
Report
Brief approved by the director
Case key
120747

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-3148  66/10/12   SUTTON W VA         CESSNA 140A         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 32, 63 TOTAL
        TIME - 1710                    N5619C              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 9 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SUTTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5619C
Reported as
Cessna 140A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sutton

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.