NYC69D0380

NTSB accident investigation · Luscombe 8E · Dexter, ME · March 23, 1969

Accident · No injuriesClosed
Date
March 23, 1969
Place
Dexter, ME · DEXTER, ME
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2618KLuscombe 8E
Status
Completed · report May 20, 1969
Report
Brief approved by the director
Case key
190874

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-0496  69/3/23    DEXTER,ME           LUSCOMBE 8E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 120
        TIME - 1400                    N2618K              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 60 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DEXTER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: SNOWBANK                                  LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N2618K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Dexter

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.