SEA66F0120

NTSB accident investigation · Piper PA-22 · Beavercreek, OR · August 31, 1965

Accident · Serious injuriesClosed
Date
August 31, 1965
Place
Beavercreek, OR · BEAVERCREEK, OR
Injuries
1 serious, 1 minor
Damage
Destroyed
Phase of flight
Approach
Aircraft
N4769ZPiper PA-22
Status
Completed · report December 6, 1965
Report
Brief approved by the director
Case key
176360

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
----------------------------------------------------------------------------------------------------------------------------
2-0641  65/8/31    BEAVERCREEK OREG    PIPER PA-22         CR-  0  1  1  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1840                    N4769Z              PX-  0  0  0  DUAL                      AGE 48, 8000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            600 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - HIGHLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           DUAL STUDENT - MISJUDGED DISTANCE AND ALTITUDE
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N4769Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Highland

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.