NYC66D0296

NTSB accident investigation · Cessna 175 · Bedford, PA · September 26, 1965

Accident · No injuriesClosed
Date
September 26, 1965
Place
Bedford, PA · BEDFORD, PA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N7036MCessna 175
Status
Completed · report November 19, 1965
Report
Brief approved by the director
Case key
175732

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-2935  65/9/26    BEDFORD PA          CESSNA 175          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 39, 15 TOTAL
        TIME - 1740                    N7036M              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BEDFORD
        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
N7036M
Reported as
Cessna 175
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bedford

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.