SEA68F0228

NTSB accident investigation · Cessna 172 · Yamhill, OR · October 16, 1967

Accident · No injuriesClosed
Date
October 16, 1967
Place
Yamhill, OR · YAMHILL, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N1621FCessna 172
Status
Completed · report April 22, 1968
Report
Brief approved by the director
Case key
112461

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-4710  67/10/16   YAMHILL,OREG        CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 26, 24 TOTAL
        TIME - 1445                    N1621F              PX-  0  0  0  TRAINING                  HOURS, 15 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAKEOFF: RUN
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - ROUGH/UNEVEN
        REMARKS- T/O FROM NARROW TRACTOR ACCESS ROAD AFTER PREVIOUS UNAUTHORIZED LNDG. STRUCK TRACTOR RUTS,VEERED.

Aircraft

Registration
N1621F
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.