MIA66F0237

NTSB accident investigation · Piper PA-23 · San Juan, PR · August 23, 1965

Accident · No injuriesClosed
Date
August 23, 1965
Place
San Juan, PR · SAN JUAN, PR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4325YPiper PA-23
Status
Completed · report October 25, 1965
Report
Brief approved by the director
Case key
176112

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-2648  65/8/23    SAN JUAN PR         PIPER PA-23         CR-  0  0  2  INSTRUCTIONAL             AIRLINE TRANSPORT, AGE
        TIME - 1835                    N4325Y              PX-  0  0  0  DUAL                      30, 1775 TOTAL HOURS, 200
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - SAN JUAN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N4325Y
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
San Juan

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.