UNK64X4061

NTSB accident investigation · Piper PA22 · Sparks, NV · September 20, 1964

Accident · No injuriesClosed
Date
September 20, 1964
Place
Sparks, NV · SPARKS, NV
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7144DPiper PA22
Status
Completed · report November 13, 1964
Report
Brief approved by the director
Case key
181220

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-2959  64/9/20    SPARKS NEV          PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 34, 163
        TIME - 0950                    N7144D              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - VISTA
        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
N7144D
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Vista

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.