MKC68D0598

NTSB accident investigation · Gibson Mong MS-2 · Carl Junction, MO · March 24, 1968

Accident · Minor injuriesClosed
Date
March 24, 1968
Place
Carl Junction, MO · CARL JUNCTION, MO
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N128GGibson Mong MS-2
Status
Completed · report July 8, 1968
Report
Brief approved by the director
Case key
110393

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-1468  68/3/24    CARL JUNCTION,MO    GIBSON MONG MS-2    CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 5154
        TIME - 1700                    N128G               PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: ACROBATICS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
           PILOT IN COMMAND - MISJUDGED ALTITUDE
        REMARKS- DURING SPIN RECOVERY ACFT ENTERED SECONDARY SPIN.STRUCK TREES ON PULLOUT.

Aircraft

Registration
N128G
Reported as
Gibson Mong MS-2
Category
Airplane, amateur-built
Engine
reciprocating
Damage
Substantial damage

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.