CHI73FEC19

NTSB accident investigation · Lash A-65 · Lakeville, MI · December 26, 1972

Accident · Minor injuriesClosed
Date
December 26, 1972
Place
Lakeville, MI · LAKEVILLE, MI
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N6389TLash A-65
Status
Completed · report March 30, 1973
Report
Brief approved by the director
Case key
169285

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-3873  72/12/26   LAKEVILLE,MICH      LASH A-65           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 840
        TIME - 1015                    N6389T              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 6 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          TROY,MICH                   LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
        FACTOR(S)
           TERRAIN - OTHER
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- ATMTD LDG ON FROZEN LAKE.DECIDED SURFACE UNSAFE.

Aircraft

Registration
N6389T
Reported as
Lash A-65
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.