OAK72DVD13

NTSB accident investigation · Schweizer 2-32 · Fremont, CA · August 28, 1971

Accident · Serious injuriesClosed
Date
August 28, 1971
Place
Fremont, CA · FREMONT, CA
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N9858ESchweizer 2-32
Status
Completed · report April 10, 1972
Report
Brief approved by the director
Case key
163417

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-3218  71/8/28    FREMONT,CALIF       SCHWEIZER 2-32      CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 52, 93 TOTAL
        TIME - 1730                    N9858E              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 29 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FREMONT
        DEPARTURE POINT             INTENDED DESTINATION
          FREMONT,CALIF               LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- GLIDER STALLED WHILE SLOPE SOARING. INSUF ALT TO RECOVER.

Aircraft

Registration
N9858E
Reported as
Schweizer 2-32
Category
Glider
Engine
none
Damage
Substantial damage
Airport
Fremont

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.