UNK65X0595

NTSB accident investigation · Luscombe 8A · Quinton, VA · November 7, 1964

Accident · No injuriesClosed
Date
November 7, 1964
Place
Quinton, VA · QUINTON, VA
Injuries
2 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N25106Luscombe 8A
Status
Completed · report December 7, 1964
Report
Brief approved by the director
Case key
181023

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-3422   64/11/7   QUINTON VA          LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 25, 900
        TIME - 1605                    N25106              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 6 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - NEW KENT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N25106
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
New Kent

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.