SEA67F0041

NTSB accident investigation · Cessna 172 · Ocean Shores, WA · May 8, 1966

Accident · Serious injuriesClosed
Date
May 8, 1966
Place
Ocean Shores, WA · OCEAN SHORES, WA
Injuries
2 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N5949ACessna 172
Status
Completed · report January 26, 1967
Report
Brief approved by the director
Case key
172476

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
----------------------------------------------------------------------------------------------------------------------------
2-0442   66/5/8    OCEAN SHORES WASH   CESSNA 172          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 49, 530
        TIME - 1130                    N5949A              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 200 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - COPALIS BCH EMERG
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
         FIRE AFTER IMPACT
        REMARKS- ACFT STALLED IN A STEEP DOWNWIND CLIMBING TURN TO AVOID BLUFF AND FOG PILOT SAW BEFORE TAKEOFF.

Aircraft

Registration
N5949A
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Copalis Bch Emerg

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.