DEN69F0015

NTSB accident investigation · Piper PA-22 · Roswell, NM · June 10, 1968

Accident · No injuriesClosed
Date
June 10, 1968
Place
Roswell, NM · ROSWELL, NM
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1687PPiper PA-22
Status
Completed · report July 30, 1968
Report
Brief approved by the director
Case key
110269

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-1649  68/6/10    ROSWELL,N MEX       PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 33, 33 TOTAL
        TIME - 1025                    N1687P              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ROSWELL
        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 RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1687P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Roswell

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.