SEA65F0021

NTSB accident investigation · Cessna 172 · Pullman, WA · March 4, 1965

Accident · No injuriesClosed
Date
March 4, 1965
Place
Pullman, WA · PULLMAN, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7200TCessna 172
Status
Completed · report June 16, 1965
Report
Brief approved by the director
Case key
178788

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-0868   65/3/4    PULLMAN WASH        CESSNA 172          CR-  0  0  2  INSTRUCTIONAL             ATP,FLIGHT INSTR., AGE
        TIME - 1500                    N7200T              PX-  0  0  0  DUAL                      40, 5400 TOTAL HOURS, 200
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PULLMAN-MOSCOW
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - IMPROPER LEVEL OFF
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N7200T
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pullman-Moscow

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.