NYC65F0039

NTSB accident investigation · Cessna 150 · Hanover, NJ · January 31, 1965

Accident · No injuriesClosed
Date
January 31, 1965
Place
Hanover, NJ · HANOVER, NJ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6504TCessna 150
Status
Completed · report March 16, 1965
Report
Brief approved by the director
Case key
180725

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-0213  65/1/31    HANOVER NJ          CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 24, 12 TOTAL
        TIME - 1720                    N6504T              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HANOVER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
        REMARKS- STUDENT ON FIRST SOLO FLIGHT.

Aircraft

Registration
N6504T
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hanover

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.