UNK64X3856

NTSB accident investigation · Luscombe 8A · Wellsville, OH · September 7, 1964

Accident · No injuriesClosed
Date
September 7, 1964
Place
Wellsville, OH · WELLSVILLE, OH
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N2565KLuscombe 8A
Status
Completed · report November 9, 1964
Report
Brief approved by the director
Case key
182100

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-2819   64/9/7    WELLSVILLE OHIO     LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 45, 200
        TIME - 1630                    N2565K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JOHNSON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2565K
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Johnson

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.