MIA67F0430

NTSB accident investigation · Piper PA-28 · Clearwater, FL · February 19, 1967

Accident · No injuriesClosed
Date
February 19, 1967
Place
Clearwater, FL · CLEARWATER, FL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8429WPiper PA-28
Status
Completed · report July 28, 1967
Report
Brief approved by the director
Case key
119008

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-0529  67/2/19    CLEARWATER,FLA      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 46, 50 TOTAL
        TIME - 1600                    N8429W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CLEARWATER
        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
N8429W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clearwater

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.