OAK67F0212

NTSB accident investigation · Cessna 182J · San Jose, CA · January 31, 1967

Accident · No injuriesClosed
Date
January 31, 1967
Place
San Jose, CA · SAN JOSE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N3415FCessna 182J
Status
Completed · report June 26, 1967
Report
Brief approved by the director
Case key
118759

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-0300  67/1/31    SAN JOSE,CALIF      CESSNA 182J         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 89 TOTAL
        TIME - 0750                    N3415F              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 8 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SANJOSE MUNI.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: PARKED AIRCRAFT                           TAXI: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER STARTING PROCEDURES
           MISCELLANEOUS ACTS,CONDITIONS - ACTION,LACK OF
        REMARKS- PARKED ACFT-N2403J,N5572Q,N1994Z,N1700D,N1216Z, N8239W,SUBST DAMAGE-N8447S,MINOR DAMAGE.

Aircraft

Registration
N3415F
Reported as
Cessna 182J
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sanjose Muni.

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.