OAK66F0231

NTSB accident investigation · Cessna 150 · Richvale, CA · April 18, 1966

Accident · Minor injuriesClosed
Date
April 18, 1966
Place
Richvale, CA · RICHVALE, CA
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8340GCessna 150
Status
Completed · report May 6, 1966
Report
Brief approved by the director
Case key
172573

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-0672  66/4/18    RICHVALE CALIF      CESSNA 150          CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1745                    N8340G              PX-  0  0  0  DUAL                      AGE 34, 3800 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            417 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - RICHVALE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           DUAL STUDENT - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N8340G
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Richvale

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.