SEA67A0004

NTSB accident investigation · Cessna 172B · Roy, MT · July 8, 1966

Accident · FatalClosed
Date
July 8, 1966
Place
Roy, MT · ROY, MT
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N7834XCessna 172B
Status
Completed · report February 15, 1967
Report
Brief approved by the director
Case key
171702

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-0557   66/7/8  NR.ROY MONT           CESSNA 172B         CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - UNK/NR                  N7834X              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 41, 2000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            884 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        MISSING AIRCRAFT - LATER RECOVERED
        REMARKS- RECOVERY DATE 8-30-66. PILOT DRANK INTOXICANTS EVE PRIOR TO 0400 TAKEOFF. HAD NOT SLEPT FOR 24 HRS

Aircraft

Registration
N7834X
Reported as
Cessna 172B
Category
Airplane
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.