MKC65F0131

NTSB accident investigation · Piper PA-22 · Sutherland, NE · May 6, 1965

Accident · No injuriesClosed
Date
May 6, 1965
Place
Sutherland, NE · SUTHERLAND, NE
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3052ZPiper PA-22
Status
Completed · report June 25, 1965
Report
Brief approved by the director
Case key
177720

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-1006   65/5/6    SUTHERLAND NEBR     PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 46, 160
        TIME - 1730                    N3052Z              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 6 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SUTHERLAND STRIP
        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
N3052Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sutherland Strip

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.