SEA66D0206

NTSB accident investigation · Cessna 150 · Scappoose, OR · January 18, 1966

Accident · No injuriesClosed
Date
January 18, 1966
Place
Scappoose, OR · SCAPPOOSE, OR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7024XCessna 150
Status
Completed · report March 15, 1966
Report
Brief approved by the director
Case key
173701

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-0157  66/1/18    SCAPPOOSE OREG      CESSNA 150          CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 2000                    N7024X              PX-  0  0  0  DUAL                      AGE 41, 4200 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            1200 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - COLUMBIA COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: ANIMALS                                   TAKEOFF: RUN
        PROBABLE CAUSE(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: HIDDEN HAZARD
        REMARKS- COLLIDED WITH LARGE DOG.NIGHT OPERATION

Aircraft

Registration
N7024X
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Columbia County

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.