DIA69D0100

NTSB accident investigation · Piper PA-28 · Chester, MD · November 1, 1968

Accident · Minor injuriesClosed
Date
November 1, 1968
Place
Chester, MD · CHESTER, MD
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6543WPiper PA-28
Status
Completed · report January 6, 1969
Report
Brief approved by the director
Case key
107492

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-3972   68/11/1   CHESTER,MD          PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 54, 600
        TIME - 1820                    N6543W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 34 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CASTLE MARINA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N6543W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Castle Marina

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.