MIA65D0063

NTSB accident investigation · Piper PA-28 · Atlanta, GA · February 27, 1965

Accident · No injuriesClosed
Date
February 27, 1965
Place
Atlanta, GA · ATLANTA, GA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6220WPiper PA-28
Status
Completed · report May 25, 1965
Report
Brief approved by the director
Case key
179035

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-0675  65/2/27    ATLANTA GA          PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 52 TOTAL
        TIME - 1205                    N6220W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 1 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DEKALB-PEACHTTREE
        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
N6220W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Dekalb-Peachttree

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.