LAX69F0069

NTSB accident investigation · Cherokee 11 · Pearblossom, CA · July 10, 1968

Accident · FatalClosed
Date
July 10, 1968
Place
Pearblossom, CA · PEARBLOSSOM, CA
Injuries
1 fatal
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N3118GCherokee 11
Status
Completed · report September 17, 1968
Report
Brief approved by the director
Case key
110043

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-2238  68/7/10    PEARBLOSSOM,CALIF   CHEROKEE 11         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 50, 382
        TIME - 1103                    N3118G              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 11 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CRYSTALAIRE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
        REMARKS- GLIDER OBSERVED MAKING SLOW TURNS AT LOW ALT PRIOR TO LOSS OF CONTROL.

Aircraft

Registration
N3118G
Reported as
Cherokee 11
Category
Glider
Engine
none
Damage
Substantial damage
Airport
Crystalaire

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.