CHI68D0485

NTSB accident investigation · Piper PA-22 · Greenwood, IN · September 23, 1967

Accident · No injuriesClosed
Date
September 23, 1967
Place
Greenwood, IN · GREENWOOD, IN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3656PPiper PA-22
Status
Completed · report January 25, 1968
Report
Brief approved by the director
Case key
113978

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-4226  67/9/23    GREENWOOD,IND       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 130
        TIME - 1500                    N3656P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SKYWAY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3656P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Skyway

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.