DEN66F0015

NTSB accident investigation · Grasshopper D-8 · Heber, UT · June 12, 1965

Accident · No injuriesClosed
Date
June 12, 1965
Place
Heber, UT · HEBER, UT
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N5053KGrasshopper D-8
Status
Completed · report August 4, 1965
Report
Brief approved by the director
Case key
177377

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-1427  65/6/12    HEBER UT            GRASSHOPPER D-8     CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 35, 20 TOTAL
        TIME - 1630                    N5053K              PX-  0  0  0  PRACTICE                  HOURS, 10 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HEVER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
        PROBABLE CAUSE(S)
          SYSTEMS-INFLIGHT FAILURE OF AILERON BELCRANK HORNS
           PERSONNEL - PRODUCTION-DESIGN-PERSONNEL: POOR/INADEQUATE DESIGN
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.
        REMARKS- GLIDER STRUCK ROCK ON LANDING.

Aircraft

Registration
N5053K
Reported as
Grasshopper D-8
Category
Glider, amateur-built
Engine
none
Damage
Destroyed
Airport
Hever

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.