CHI68F0328

NTSB accident investigation · Piper PA-22 · Wabash, IN · September 24, 1967

Accident · No injuriesClosed
Date
September 24, 1967
Place
Wabash, IN · WABASH, IN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6999BPiper PA-22
Status
Completed · report December 18, 1967
Report
Brief approved by the director
Case key
113787

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-3515  67/9/24    WABASH,IND          PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 29, 16 TOTAL
        TIME - 1100                    N6999B              PX-  0  0  0  TRAINING                  HOURS, 12 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - WABASH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6999B
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Wabash

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.