MIA68F0279

NTSB accident investigation · Piper PA-32 · Humacao, PR · November 12, 1967

Accident · No injuriesClosed
Date
November 12, 1967
Place
Humacao, PR
Injuries
2 uninjured
Damage
Destroyed
Phase of flight
Approach
Aircraft
N4041WPiper PA-32
Status
Completed · report January 15, 1968
Report
Brief approved by the director
Case key
112788

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-4052  67/11/12   HUMACAO,PR          PIPER PA-32         CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, FL.INSTR.,
        TIME - 1500                    N4041W              PX-  0  0  1  PARAJUMP-SPORT            AGE 24, 1000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            10 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - HUMACAO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: DITCHES                                   LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE

Aircraft

Registration
N4041W
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Destroyed
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.