MKC68F0054

NTSB accident investigation · Beech 35 · Sidney, NE · June 27, 1967

Accident · No injuriesClosed
Date
June 27, 1967
Place
Sidney, NE · SIDNEY, NE
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4842VBeech 35
Status
Completed · report October 5, 1967
Report
Brief approved by the director
Case key
116284

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-2222  67/6/27    SIDNEY,NEBR         BEECH 35            CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 39, 69 TOTAL
        TIME - 1226                    N4842V              PX-  0  0  0  TRAINING                  HOURS, 61 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SIDNEY MUNI.
        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
N4842V
Reported as
Beech 35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sidney Muni.

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.