SEA67F0040

NTSB accident investigation · Cessna 172C · Maupin, OR · May 17, 1966

Accident · No injuriesClosed
Date
May 17, 1966
Place
Maupin, OR · MAUPIN, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N8467XCessna 172C
Status
Completed · report December 7, 1966
Report
Brief approved by the director
Case key
171994

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-2906  66/5/17    MAUPIN OREG         CESSNA 172C         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 23, 46 TOTAL
        TIME - 1715                    N8467X              PX-  0  0  0  PRACTICE                  HOURS, 8 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - HIGH VEGETATION
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER
        REMARKS- STUDENT ATTEMPTED TAKEOFF FROM 900 FOOT LONG FIELD WITH WHEAT 6 INCHES HIGH.

Aircraft

Registration
N8467X
Reported as
Cessna 172C
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.