SEA66A0054

NTSB accident investigation · Piper PA-16 · Sutherlin, OR · May 6, 1966

Accident · FatalClosed
Date
May 6, 1966
Place
Sutherlin, OR · SUTHERLIN, OR
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N5744HPiper PA-16
Status
Completed · report October 19, 1966
Report
Brief approved by the director
Case key
172393

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-0289   66/5/6    SUTHERLIN ORE       PIPER PA-16         CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1015                    N5744H              PX-  0  0  0  BUSINESS                  AGE 41, 4113 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            22 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - MUNICIPAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INCAPACITATION
           MISCELLANEOUS ACTS,CONDITIONS - PILOT SUFFERED HEART ATTACK

Aircraft

Registration
N5744H
Reported as
Piper PA-16
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Municipal

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.