DIA68F0026

NTSB accident investigation · Piper PA-28 · Aberdeen, MD · June 23, 1967

Accident · No injuriesClosed
Date
June 23, 1967
Place
Aberdeen, MD · ABERDEEN, MD
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6614WPiper PA-28
Status
Completed · report September 27, 1967
Report
Brief approved by the director
Case key
116217

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-2120  67/6/23    ABERDEEN,MD         PIPER PA-28         CR-  0  0  2  NONCOMMERCIAL             PRIVATE, AGE 29, 195
        TIME - 1830                    N6614W              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PHILLIPS AAF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6614W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Phillips Aaf

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.