SEA66A0051

NTSB accident investigation · Hughes 269B · Beaver, OR · April 19, 1966

Accident · FatalClosed
Date
April 19, 1966
Place
Beaver, OR · BEAVER, OR
Injuries
3 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N9363FHughes 269B
Status
Completed · report August 22, 1966
Report
Brief approved by the director
Case key
172358

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-0218  66/4/19  NR.BEAVER OREG        HUGHES 269B         CR-  1  0  0  COMMERCIAL                COMMERCIAL, AGE 34, 2000
        TIME - 0815                    N9363F              PX-  2  0  0  OTHER                     TOTAL HOURS, 300 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE
         FIRE AFTER IMPACT
        REMARKS- STREAM SURVEY FOR OREG.FISH COMMISSION.

Aircraft

Registration
N9363F
Reported as
Hughes 269B
Category
Helicopter
Engine
reciprocating
Damage
Destroyed

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.