MKC66D0469

NTSB accident investigation · Chanpion 7FC · Hopkins, MN · February 5, 1966

Accident · No injuriesClosed
Date
February 5, 1966
Place
Hopkins, MN · HOPKINS, MN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9072BChanpion 7FC
Status
Completed · report August 26, 1966
Report
Brief approved by the director
Case key
172791

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-1654   66/2/5    HOPKINS MINN        CHANPION 7FC        CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 80 TOTAL
        TIME - 1205                    N9072B              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 17 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FLYING CLOUD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N9072B
Reported as
Chanpion 7FC
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Flying Cloud

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.