MKC67F0603

NTSB accident investigation · Cessna 172 · Shelton, NE · May 7, 1967

Accident · Minor injuriesClosed
Date
May 7, 1967
Place
Shelton, NE · SHELTON, NE
Injuries
1 minor
Damage
Destroyed
Phase of flight
Landing
Aircraft
N6750ACessna 172
Status
Completed · report September 20, 1967
Report
Brief approved by the director
Case key
117306

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-1750   67/5/7    SHELTON, NEBR       CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 36, 137
        TIME - 2000                    N6750A              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 130 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DUBBS FARM STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6750A
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Dubbs Farm Strip

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.