OAK69D0188

NTSB accident investigation · Cessna 150 · San Jose, CA · October 27, 1968

Accident · No injuriesClosed
Date
October 27, 1968
Place
San Jose, CA · SAN JOSE, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N22444Cessna 150
Status
Completed · report January 15, 1969
Report
Brief approved by the director
Case key
107502

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-3988  68/10/27   SAN JOSE,CALIF      CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 28, 54 TOTAL
        TIME - 1030                    N22444              PX-  0  0  0  TRAINING                  HOURS, 10 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - REID-HILLVIEW
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAXI: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER STARTING PROCEDURES
           PILOT IN COMMAND - IMPROPER OPERATION OF POWERPLANT & POWERPLANT CONTROLS
        REMARKS- ENG STARTED AT HIGH THROTTLE SETTING,NO CORRECTIVE ACTION TAKEN.

Aircraft

Registration
N22444
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Reid-Hillview

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.