MKC68F0550

NTSB accident investigation · Beech A23 · Columbus, NE · May 24, 1968

Accident · No injuriesClosed
Date
May 24, 1968
Place
Columbus, NE · COLUMBUS, NE
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8861MBeech A23
Status
Completed · report June 14, 1968
Report
Brief approved by the director
Case key
110701

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-1264  68/5/24    COLUMBUS,NEBR       BEECH A23           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 24, 50 TOTAL
        TIME - 1805                    N8861M              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - COLUMBUS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8861M
Reported as
Beech A23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Columbus

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.