DIA70D0018

NTSB accident investigation · Cessna 177 · Darnestown, MD · June 28, 1969

Accident · Minor injuriesClosed
Date
June 28, 1969
Place
Darnestown, MD · DARNESTOWN, MD
Injuries
1 minor, 2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3140TCessna 177
Status
Completed · report August 4, 1969
Report
Brief approved by the director
Case key
180282

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-1738  69/6/28    DARNESTOWN,MD       CESSNA 177          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 29, 170
        TIME - 1830                    N3140T              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 49 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CLARK BOYER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N3140T
Reported as
Cessna 177
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clark Boyer

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.