LAX68D0189

NTSB accident investigation · Schweizer SGS126 · Pearblossom, CA · October 15, 1967

Accident · No injuriesClosed
Date
October 15, 1967
Place
Pearblossom, CA · PEARBLOSSOM, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3839ASchweizer SGS126
Status
Completed · report December 29, 1967
Report
Brief approved by the director
Case key
112739

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-4006  67/10/15   PEARBLOSSOM,CALIF   SCHWEIZER SGS126    CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 70 TOTAL
        TIME - 1410                    N3839A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 50 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CRYSTAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: TREES                                     LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- PLT MISCALCULATED WIND AND LIFT AVAILABLE.

Aircraft

Registration
N3839A
Reported as
Schweizer SGS126
Category
Glider
Engine
none
Damage
Substantial damage
Airport
Crystal

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.