UNK64X2077

NTSB accident investigation · Piper PA28 · Williston, ND · June 2, 1964

Accident · No injuriesClosed
Date
June 2, 1964
Place
Williston, ND · WILLISTON, ND
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7167WPiper PA28
Status
Completed · report September 28, 1964
Report
Brief approved by the director
Case key
183805

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-1505   64/6/2    WILLISTON N DAK     PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 40, 63 TOTAL
        TIME - 1030                    N7167W              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - WRIGHT
        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
N7167W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Wright

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.