MIA66D0486

NTSB accident investigation · Piper PA-28 · Ft Lauderdale, FL · March 19, 1966

Accident · No injuriesClosed
Date
March 19, 1966
Place
Ft Lauderdale, FL · FT LAUDERDALE, FL
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7831WPiper PA-28
Status
Completed · report May 9, 1966
Report
Brief approved by the director
Case key
173223

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-0644  66/3/19    FT LAUDERDALE FLA   PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 142
        TIME - 1415                    N7831W              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 102 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FT LAUDERDALE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7831W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ft Lauderdale

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.