CHI66D0319

NTSB accident investigation · Cessna 150 · Crawfordsville, IN · September 24, 1965

Accident · No injuriesClosed
Date
September 24, 1965
Place
Crawfordsville, IN · CRAWFORDSVILLE, IN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1160YCessna 150
Status
Completed · report November 9, 1965
Report
Brief approved by the director
Case key
175637

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-2824  65/9/24    CRAWFORDSVILLE IN   CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 22, 18 TOTAL
        TIME - 1800                    N1160Y              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CRAWFORDSVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1160Y
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Crawfordsville

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.