MIA66F0377

NTSB accident investigation · Piper PA-24 · Orlando, FL · December 24, 1965

Accident · No injuriesClosed
Date
December 24, 1965
Place
Orlando, FL · ORLANDO, FL
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5006PPiper PA-24
Status
Completed · report February 4, 1966
Report
Brief approved by the director
Case key
174236

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-3672  65/12/24   ORLANDO FLA         PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 80 TOTAL
        TIME - 1145                    N5006P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 78 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HERNDON
        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
N5006P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Herndon

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.