DEN68D0112

NTSB accident investigation · Cessna 172 · Boulder, CO · September 30, 1967

Accident · No injuriesClosed
Date
September 30, 1967
Place
Boulder, CO · BOULDER, CO
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2569LCessna 172
Status
Completed · report December 18, 1967
Report
Brief approved by the director
Case key
113766

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-3480  67/9/30    BOULDER,COLO        CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 39 TOTAL
        TIME - 1000                    N2569L              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 2 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BOULDER MUNI
        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
N2569L
Reported as
Cessna 172
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.