CHI70A0010

NTSB accident investigation · Champion 7GCAA · Salem, IN · July 26, 1969

Accident · FatalClosed
Date
July 26, 1969
Place
Salem, IN · SALEM, IN
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N9625SChampion 7GCAA
Status
Completed · report February 16, 1970
Report
Brief approved by the director
Case key
165871

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-3048  69/7/26    SALEM,IND           CHAMPION 7GCAA      CR-  2  0  0  NONCOMMERCIAL             PRIVATE, AGE 53, 928
        TIME - 1900                    N9625S              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 208 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          SALEM,IND                   SALEM,IND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: ACROBATICS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
         FIRE AFTER IMPACT
        REMARKS- PERFORMING LOW LEVEL SLOW ROLL.

Aircraft

Registration
N9625S
Reported as
Champion 7GCAA
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.