MIA66F0337

NTSB accident investigation · Luscombe 8A · Orlando, FL · November 27, 1965

Accident · Minor injuriesClosed
Date
November 27, 1965
Place
Orlando, FL · ORLANDO, FL
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N1539BLuscombe 8A
Status
Completed · report January 13, 1966
Report
Brief approved by the director
Case key
174669

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-3507  65/11/27   ORLANDO FLA         LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 25, 24 TOTAL
        TIME - 1215                    N1539B              PX-  0  0  0  PRACTICE                  HOURS, 19 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HOEQUIST
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - GUST LOCKS ENGAGED
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        REMARKS- RIGHT SIDE STICK SECURED WITH SEAT BELT.

Aircraft

Registration
N1539B
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hoequist

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.