MKC66F0223

NTSB accident investigation · Beechcraft 23 · Wichita, KS · September 1, 1965

Accident · No injuriesClosed
Date
September 1, 1965
Place
Wichita, KS · WICHITA, KS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2347ZBeechcraft 23
Status
Completed · report December 8, 1965
Report
Brief approved by the director
Case key
175265

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-3179   65/9/1    WICHITA KANS        BEECHCRAFT 23       CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 44, 250
        TIME - 1335                    N2347Z              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 75 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - RAWDON
        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
N2347Z
Reported as
Beechcraft 23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rawdon

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.