CHI67A0029

NTSB accident investigation · Schemp SHK-1 · Saginaw, MI · August 28, 1966

Accident · FatalClosed
Date
August 28, 1966
Place
Saginaw, MI · SAGINAW, MI
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N30055Schemp SHK-1
Status
Completed · report March 23, 1967
Report
Brief approved by the director
Case key
122493

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
----------------------------------------------------------------------------------------------------------------------------
2-0760  66/8/28    SAGINAW MICH        SCHEMP SHK-1        CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 29, 496
        TIME - 1241                    N30055              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 3 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SAGINAW MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - LACK OF FAMILIARITY WITH AIRCRAFT
        REMARKS- GLIDER STALLED WHILE ATTACHED TO LAUNCH CABLE.DURING SPIN CABLE RELEASED ABOUT 100 FT ABOVE GRND.

Aircraft

Registration
N30055
Reported as
Schemp SHK-1
Category
Glider
Engine
none
Damage
Destroyed
Airport
Saginaw Muni

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.