MIA66F0519

NTSB accident investigation · Cessna 172 · Clemmons, NC · May 5, 1966

Accident · Minor injuriesClosed
Date
May 5, 1966
Place
Clemmons, NC · CLEMMONS, NC
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2815UCessna 172
Status
Completed · report June 7, 1966
Report
Brief approved by the director
Case key
172051

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-0893   66/5/5    CLEMMONS NC         CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 35, 21 TOTAL
        TIME - 1130                    N2815U              PX-  0  0  0  PRACTICE                  HOURS, 5 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BINGHAMS
        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 - DOWNWIND
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2815U
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Binghams

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.