DIA68D0091

NTSB accident investigation · Piper PA-20 · Oyster, VA · October 4, 1967

Accident · No injuriesClosed
Date
October 4, 1967
Place
Oyster, VA · OYSTER, VA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2247APiper PA-20
Status
Completed · report December 22, 1967
Report
Brief approved by the director
Case key
113859

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-3595   67/10/4   OYSTER,VA           PIPER PA-20         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 57, 448
        TIME - 1445                    N2247A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 181 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER
        REMARKS- FLOAT EQUIPPED

Aircraft

Registration
N2247A
Reported as
Piper PA-20
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.