MIA65F0039

NTSB accident investigation · Cessna 172 · Charleston, MS · April 4, 1965

Accident · No injuriesClosed
Date
April 4, 1965
Place
Charleston, MS · CHARLESTON, MS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2535YCessna 172
Status
Completed · report May 18, 1965
Report
Brief approved by the director
Case key
179001

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-0639   65/4/4    CHARLESTON MISS     CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 42, 736
        TIME - 1715                    N2535Y              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 42 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SAYLES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N2535Y
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sayles

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.