MIA66A0001

NTSB accident investigation · Piper PA-32 · Vero Beach, FL · July 1, 1965

Accident · FatalClosed
Date
July 1, 1965
Place
Vero Beach, FL · VERO BEACH, FL
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N9998WPiper PA-32
Status
Completed · report November 18, 1965
Report
Brief approved by the director
Case key
177257

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
----------------------------------------------------------------------------------------------------------------------------
2-0605   65/7/1    VERO BEACH FLA      PIPER PA-32         CR-  1  0  0  MISCELLANEOUS             ATP,FLIGHT INSTR., AGE
        TIME - 1606                    N9998W              PX-  0  0  0  EXPERIMENTATION           33, 4030 TOTAL HOURS, 205
                                       DAMAGE-DESTROYED    OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - VERO BEACH MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - PILOT SUFFERED HEART ATTACK
           PILOT IN COMMAND - INCAPACITATION
         FIRE AFTER IMPACT

Aircraft

Registration
N9998W
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Vero Beach Muni

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.