SEA67D0124

NTSB accident investigation · Cessna 182 · Tacoma, WA · August 12, 1966

Accident · No injuriesClosed
Date
August 12, 1966
Place
Tacoma, WA · TACOMA, WA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2371RCessna 182
Status
Completed · report February 28, 1967
Report
Brief approved by the director
Case key
121293

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-3676  66/8/12    TACOMA WASH         CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 50, 260
        TIME - 0600                    N2371R              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TACOMA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2371R
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Tacoma

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.