MKC66F0333

NTSB accident investigation · Piper PA-22 · Cape Girardeau, MO · November 11, 1965

Accident · No injuriesClosed
Date
November 11, 1965
Place
Cape Girardeau, MO · CAPE GIRARDEAU, MO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N3968PPiper PA-22
Status
Completed · report March 25, 1966
Report
Brief approved by the director
Case key
174380

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-3883  65/11/11   CAPE GIRARDEAU MO   PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 34, 17 TOTAL
        TIME - 0915                    N3968P              PX-  0  0  0  SOLO                      HOURS, 13 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CAPE GIRARDEAU
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3968P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Cape Girardeau

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.