DEN67F0094

NTSB accident investigation · Schweizer TG-3A · Casper, WY · August 28, 1966

Accident · Serious injuriesClosed
Date
August 28, 1966
Place
Casper, WY · CASPER, WY
Injuries
1 serious, 1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9305HSchweizer TG-3A
Status
Completed · report October 24, 1966
Report
Brief approved by the director
Case key
171637

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-0373  66/8/28    CASPER WYO          SCHWEIZER TG-3A     CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 41, 205
        TIME - 1330                    N9305H              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 5 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CASPER AIR TERMIN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED ALTITUDE
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PILOT ATTEMPTED A 360-DEGREE TURN WITH INSUFFICIENT ALTITUDE.

Aircraft

Registration
N9305H
Reported as
Schweizer TG-3A
Category
Glider
Engine
none
Damage
Substantial damage
Airport
Casper Air Termin

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.