FTW67F0109

NTSB accident investigation · Luscombe 8A · Enid, OK · July 23, 1966

Accident · No injuriesClosed
Date
July 23, 1966
Place
Enid, OK · ENID, OK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N71533Luscombe 8A
Status
Completed · report September 28, 1966
Report
Brief approved by the director
Case key
122089

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-2041  66/7/23    ENID OKLA           LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 78 TOTAL
        TIME - 1525                    N71533              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 4 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - WOODRING FLD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N71533
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Woodring Fld

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.