DEN67D0215

NTSB accident investigation · Beech 23 · Boulder, CO · February 12, 1967

Accident · No injuriesClosed
Date
February 12, 1967
Place
Boulder, CO · BOULDER, CO
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2383JBeech 23
Status
Completed · report July 18, 1967
Report
Brief approved by the director
Case key
118888

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-0420  67/2/12    BOULDER,COLO        BEECH 23            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 31, 105
        TIME - 1715                    N2383J              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 38 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BOULDER MUNI.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           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
N2383J
Reported as
Beech 23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Boulder 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.