FTW67D0647

NTSB accident investigation · Champion 7GCAA · San Antonio, TX · June 18, 1967

Accident · No injuriesClosed
Date
June 18, 1967
Place
San Antonio, TX · SAN ANTONIO, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8383VChampion 7GCAA
Status
Completed · report September 28, 1967
Report
Brief approved by the director
Case key
116191

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-2096  67/6/18    SAN ANTONIO,TEX     CHAMPION 7GCAA      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 49, 303
        TIME - 1225                    N8383V              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TWIN OAKS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8383V
Reported as
Champion 7GCAA
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Twin Oaks

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.