SEA67A0068

NTSB accident investigation · Cessna 172 · Helmville, MT · May 27, 1967

Accident · FatalClosed
Date
May 27, 1967
Place
Helmville, MT · HELMVILLE, MT
Injuries
2 fatal
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N6995ACessna 172
Status
Completed · report February 8, 1968
Report
Brief approved by the director
Case key
116951

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-0915  67/5/27    HELMVILLE,MONT      CESSNA 172          CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 28, 257
        TIME - 0725                    N6995A              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 169 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - FLEW INTO BLIND CANYON
        REMARKS- PILOT FLEW INTO STEEP CANYON.

Aircraft

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