SEA68F0203

NTSB accident investigation · Beech 23 · Lakeside, OR · July 28, 1967

Accident · No injuriesClosed
Date
July 28, 1967
Place
Lakeside, OR · LAKESIDE, OR
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2346QBeech 23
Status
Completed · report September 17, 1968
Report
Brief approved by the director
Case key
114816

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-4793  67/7/28    LAKESIDE,OREG       BEECH 23            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 389
        TIME - 1800                    N2346Q              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 245 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LAKESIDE
        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
N2346Q
Reported as
Beech 23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lakeside

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.