DIA67D0108

NTSB accident investigation · Cessna 172 · Fork Union, VA · May 16, 1967

Accident · No injuriesClosed
Date
May 16, 1967
Place
Fork Union, VA · FORK UNION, VA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2776LCessna 172
Status
Completed · report September 13, 1967
Report
Brief approved by the director
Case key
116986

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-1563  67/5/16    FORK UNION,VA       CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 44, 60 TOTAL
        TIME - 0810                    N2776L              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FORK UNION
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N2776L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fork Union

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.