SEA68F0266

NTSB accident investigation · Piper PA-22 · Crescent Lk, OR · February 29, 1968

Accident · No injuriesClosed
Date
February 29, 1968
Place
Crescent Lk, OR · CRESCENT LK, OR
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7021DPiper PA-22
Status
Completed · report May 20, 1968
Report
Brief approved by the director
Case key
111485

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-0822  68/2/29    CRESCENT LK,OREG    PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 118
        TIME - 1810                    N7021D              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 48 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CRESCENT LAKE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SNOW ON RUNWAY
        REMARKS- SKIDDED ON SNOW,CONTACTED BARE SPOT THEN DEEPER SNOW ON RNWY.

Aircraft

Registration
N7021D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Crescent Lake

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.