MKC67D0503

NTSB accident investigation · Piper PA-22 · Nevada, IA · April 11, 1967

Accident · No injuriesClosed
Date
April 11, 1967
Place
Nevada, IA · NEVADA, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6875BPiper PA-22
Status
Completed · report August 31, 1967
Report
Brief approved by the director
Case key
117514

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-1123  67/4/11    NEVADA,IOWA         PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 23, 240
        TIME - 0115                    N6875B              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 70 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NEVADA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N6875B
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Nevada

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.