MIA68F0218

NTSB accident investigation · Piper PA-22 · Humacao, PR · September 23, 1967

Accident · No injuriesClosed
Date
September 23, 1967
Place
Humacao, PR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5278ZPiper PA-22
Status
Completed · report December 18, 1967
Report
Brief approved by the director
Case key
113739

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-3455  67/9/23    HUMACAO,PR          PIPER PA-22         CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, AGE 18, 397
        TIME - 1230                    N5278Z              PX-  0  0  0  FERRY                     TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HUMACAO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5278Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Humacao

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.