CHI68D0402

NTSB accident investigation · Piper PA-22 · Wonewoc, WI · September 1, 1967

Accident · Minor injuriesClosed
Date
September 1, 1967
Place
Wonewoc, WI · WONEWOC, WI
Injuries
1 minor, 2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6029DPiper PA-22
Status
Completed · report December 12, 1967
Report
Brief approved by the director
Case key
114227

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-3270   67/9/1    WONEWOC,WIS         PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 70 TOTAL
        TIME - 1910                    N6029D              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 32 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - THREE CASTLES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6029D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Three Castles

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.