UNK64X1789

NTSB accident investigation · Cessna 140 · Ellensburg, WA · May 16, 1964

Accident · No injuriesClosed
Date
May 16, 1964
Place
Ellensburg, WA · ELLENSBURG, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2432NCessna 140
Status
Completed · report September 22, 1964
Report
Brief approved by the director
Case key
183965

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-1299  64/5/16    ELLENSBURG WASH     CESSNA 140          CR-  0  0  1  INSTRUCTIONAL             PRIVATE, AGE 18, 104
        TIME - 1000                    N2432N              PX-  0  0  0  TRAINING                  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ELLENSBURG
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2432N
Reported as
Cessna 140
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ellensburg

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.