CHI66D0346

NTSB accident investigation · Cessna 182C · Strongsville, OH · September 6, 1965

Accident · Minor injuriesClosed
Date
September 6, 1965
Place
Strongsville, OH · STRONGSVILLE, OH
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N1812CCessna 182C
Status
Completed · report November 18, 1965
Report
Brief approved by the director
Case key
175712

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-2917   65/9/6    STRONGSVILLE OHIO   CESSNA 182C         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 38, 138
        TIME - 1730                    N1812C              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SPRAGUE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: FINAL APPROACH
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N1812C
Reported as
Cessna 182C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sprague

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.