SEA66F0093

NTSB accident investigation · Phillips CT-2 · Vancouver, WA · June 27, 1965

Accident · Serious injuriesClosed
Date
June 27, 1965
Place
Vancouver, WA · VANCOUVER, WA
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N19989Phillips CT-2
Status
Completed · report October 15, 1965
Report
Brief approved by the director
Case key
178205

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-0495  65/6/27    VANCOUVER WASH      PHILLIPS CT-2       CR-  0  1  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1415                    N19989              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 43, 4247 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            136 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - EVERGREEN AIRPARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N19989
Reported as
Phillips CT-2
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Evergreen Airpark

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.