UNK64X1701

NTSB accident investigation · Piper PA22 · Mesa, AZ · May 10, 1964

Accident · No injuriesClosed
Date
May 10, 1964
Place
Mesa, AZ · MESA, AZ
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1828PPiper PA22
Status
Completed · report September 18, 1964
Report
Brief approved by the director
Case key
183892

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-1233  64/5/10    MESA ARIZ           PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 48, 430
        TIME - 0930                    N1828P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FALCON FIELD
        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
N1828P
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Falcon Field

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.