NYC69F0124

NTSB accident investigation · Luscombe 8A · Fryeburg, ME · September 4, 1968

Accident · Minor injuriesClosed
Date
September 4, 1968
Place
Fryeburg, ME · FRYEBURG, ME
Injuries
1 minor, 1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N2107KLuscombe 8A
Status
Completed · report October 31, 1968
Report
Brief approved by the director
Case key
108188

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-3051   68/9/4    FRYEBURG,ME         LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 57, 353
        TIME - 1710                    N2107K              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 301 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - EASTERN SLOPE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N2107K
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Eastern Slope

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.