UNK64X3904

NTSB accident investigation · Cessna 172 · Danbury, WI · September 10, 1964

Accident · No injuriesClosed
Date
September 10, 1964
Place
Danbury, WI · DANBURY, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7586XCessna 172
Status
Completed · report November 9, 1964
Report
Brief approved by the director
Case key
182134

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-2850  64/9/10    DANBURY WIS         CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 51, 1535
        TIME - 1700                    N7586X              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JOHNSON STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7586X
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Johnson Strip

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.