MIA66D0352

NTSB accident investigation · Piper PA-18 · Ft Lauderdale, FL · November 26, 1965

Accident · No injuriesClosed
Date
November 26, 1965
Place
Ft Lauderdale, FL · FT LAUDERDALE, FL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4386APiper PA-18
Status
Completed · report January 27, 1966
Report
Brief approved by the director
Case key
174833

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-3602  65/11/26   FT LAUDERDALE FLA   PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 24, 800
        TIME - 1015                    N4386A              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 600 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FT LAUDERDALE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N4386A
Reported as
Piper PA-18
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.