MIA66F0520

NTSB accident investigation · Luscombe 8A · Fort Pierce, FL · March 31, 1966

Accident · No injuriesClosed
Date
March 31, 1966
Place
Fort Pierce, FL · FORT PIERCE, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1439BLuscombe 8A
Status
Completed · report June 2, 1966
Report
Brief approved by the director
Case key
172619

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-0788  66/3/31    FORT PIERCE FLA     LUSCOMBE 8A         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 38, 14 TOTAL
        TIME - 1605                    N1439B              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ST LUCIE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS

Aircraft

Registration
N1439B
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
St Lucie

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.