CHI66F0623

NTSB accident investigation · Luscombe 8A · Manistique, MI · February 28, 1966

Accident · No injuriesClosed
Date
February 28, 1966
Place
Manistique, MI · MANISTIQUE, MI
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1858KLuscombe 8A
Status
Completed · report April 12, 1966
Report
Brief approved by the director
Case key
173031

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-0394  66/2/28  NR.MANISTIQUE MICH    LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 469
        TIME - 1750                    N1858K              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 188 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT
                                  ADVERSE/UNFAVORABLE WEATHER
        REMARKS- NIGHT OPERATION

Aircraft

Registration
N1858K
Reported as
Luscombe 8A
Category
Airplane
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.