MIA71FKW24

NTSB accident investigation · Schweizer TG-3A · Eagleville, TN · December 5, 1970

Accident · Serious injuriesClosed
Date
December 5, 1970
Place
Eagleville, TN · EAGLEVILLE, TN
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N63904Schweizer TG-3A
Status
Completed · report September 16, 1971
Report
Brief approved by the director
Case key
159114

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-4348   70/12/5   EAGLEVILLE,TENN     SCHWEIZER TG-3A     CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 42, 1107
        TIME - 1400                    N63904              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PUCKETT FIELD
        DEPARTURE POINT             INTENDED DESTINATION
          EAGLEVILLE,TENN             EAGLEVILLE,TENN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              LANDING: TRAFFIC PATTERN-CIRCLING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N63904
Reported as
Schweizer TG-3A
Category
Glider
Engine
none
Damage
Substantial damage
Airport
Puckett Field

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.