SEA69D0045

NTSB accident investigation · Piper PA-18 · Carver, OR · May 27, 1968

Accident · No injuriesClosed
Date
May 27, 1968
Place
Carver, OR · CARVER, OR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5881DPiper PA-18
Status
Completed · report December 12, 1968
Report
Brief approved by the director
Case key
118644

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-3504  68/5/27    CARVER,OREG         PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             NO CERTIFICATE, AGE 44,
        TIME - 1910                    N5881D              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  250 TOTAL HOURS, 40 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - TROHS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           TERRAIN - HIGH VEGETATION
        REMARKS- LANDED IN FLD OF THICK HIGH ALFALFA.

Aircraft

Registration
N5881D
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Trohs

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.