SEA67F0313

NTSB accident investigation · Cessna 180 · Spokane, WA · May 18, 1967

Accident · No injuriesClosed
Date
May 18, 1967
Place
Spokane, WA · SPOKANE, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8640XCessna 180
Status
Completed · report September 14, 1967
Report
Brief approved by the director
Case key
117013

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-1585  67/5/18    SPOKANE,WASH        CESSNA 180          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1200                    N8640X              PX-  0  0  0  PRACTICE                  AGE 23, 225 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            1 IN TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - FELTS FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N8640X
Reported as
Cessna 180
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Felts Field

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.