SEA68F0299

NTSB accident investigation · Piper PA-22 · Hood River, OR · April 17, 1968

Accident · No injuriesClosed
Date
April 17, 1968
Place
Hood River, OR · HOOD RIVER, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N610APiper PA-22
Status
Completed · report July 9, 1968
Report
Brief approved by the director
Case key
110974

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-1342  68/4/17    HOOD RIVER,OREG     PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 55 TOTAL
        TIME - 1020                    N610A               PX-  0  0  0  BUSINESS                  HOURS, 43 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HOOD RIVER
        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
N610A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hood River

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.