FTW66F0087

NTSB accident investigation · Cessna 175 · Vernon, TX · June 3, 1965

Accident · Minor injuriesClosed
Date
June 3, 1965
Place
Vernon, TX · VERNON, TX
Injuries
1 minor, 1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N7386MCessna 175
Status
Completed · report August 30, 1965
Report
Brief approved by the director
Case key
177596

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-1795   65/6/3    VERNON TEX          CESSNA 175          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 35, 60 TOTAL
        TIME - 1350                    N7386M              PX-  0  0  1  PRACTICE                  HOURS, 50 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - VERNON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N7386M
Reported as
Cessna 175
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Vernon

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.