SEA67D0108

NTSB accident investigation · Cessna 180 · Conrad, MT · August 16, 1966

Accident · No injuriesClosed
Date
August 16, 1966
Place
Conrad, MT · CONRAD, MT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N4603UCessna 180
Status
Completed · report March 1, 1967
Report
Brief approved by the director
Case key
121296

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-3720  66/8/16  NR.CONRAD MONT        CESSNA 180          CR-  0  0  1  COMMERCIAL                COMMERCIAL, FL.INSTR.,
        TIME - 1500                    N4603U              PX-  0  0  0  CTR CARGO-D               AGE 44, 10000 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 5000 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - CONRAD
        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
        REMARKS- SURVEYING ROAD PREPARATORY TO LANDING.

Aircraft

Registration
N4603U
Reported as
Cessna 180
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Conrad

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.