CHI70F0013

NTSB accident investigation · Luscombe 8E · Beaverton, MI · June 1, 1969

Accident · Serious injuriesClosed
Date
June 1, 1969
Place
Beaverton, MI · BEAVERTON, MI
Injuries
1 serious, 1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N1304BLuscombe 8E
Status
Completed · report July 18, 1969
Report
Brief approved by the director
Case key
178736

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-1581   69/6/1    BEAVERTON,MICH      LUSCOMBE 8E         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 34, 130
        TIME - 2000                    N1304B              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 39 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ALBRIGHT SHORES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - FAILED TO USE ALL AVAILABLE RUNWAY

Aircraft

Registration
N1304B
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Albright Shores

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.