DIA68F0001

NTSB accident investigation · Luscombe 8A · Broomes Island, VA · May 30, 1968

Accident · Serious injuriesClosed
Date
May 30, 1968
Place
Broomes Island, VA · BROOMES ISLAND, VA
Injuries
1 serious
Damage
Destroyed
Phase of flight
Unknown
Aircraft
N71322Luscombe 8A
Status
Completed · report September 16, 1968
Report
Brief approved by the director
Case key
109996

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-2191  68/5/30    BROOMES ISLAND,VA   LUSCOMBE 8A         CR-  0  1  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1800                    N71322              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 51, 810 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            300 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     UNKNOWN/NOT REPORTED
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        MISSING AIRCRAFT - LATER RECOVERED
        REMARKS- RECOVERY DATE 6/2/68.PLT SUFFERED AMNESIA,WANDERED OUT OF WOODS ON 6/2/68.

Aircraft

Registration
N71322
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.