MIA65A0096

NTSB accident investigation · Piper PA-22 · Caguas, PR · March 27, 1965

Accident · FatalClosed
Date
March 27, 1965
Place
Caguas, PR · CAGUAS, PR
Injuries
3 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N9518DPiper PA-22
Status
Completed · report August 30, 1965
Report
Brief approved by the director
Case key
179291

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-0337  65/3/27    CAGUAS PR           PIPER PA-22         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 53, UNK/NR
        TIME - 1615                    N9518D              PX-  2  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - CAGUAS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - PILOT SUFFERED HEART ATTACK
         FIRE AFTER IMPACT
        REMARKS- PLT REPORTED 433 TOTAL FLYING HOURS 01/22/57.

Aircraft

Registration
N9518D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Caguas

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.