OAK69A0001

NTSB accident investigation · Cessna 182 · Jarbidge, NV · July 1, 1968

Accident · FatalClosed
Date
July 1, 1968
Place
Jarbidge, NV · JARBIDGE, NV
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N3204SCessna 182
Status
Completed · report September 6, 1968
Report
Brief approved by the director
Case key
109902

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
----------------------------------------------------------------------------------------------------------------------------
3-2048   68/7/1    JARBIDGE,NEV        CESSNA 182          CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 43, 2071
        TIME - 0900                    N3204S              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1016 IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
         FIRE AFTER IMPACT
        REMARKS- STRUCK POWER CABLE STRUNG ACROSS CANYON.

Aircraft

Registration
N3204S
Reported as
Cessna 182
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.