CHI66D0673

NTSB accident investigation · Piper PA-22 · Ontonagon, MI · April 16, 1966

Accident · No injuriesClosed
Date
April 16, 1966
Place
Ontonagon, MI · ONTONAGON, MI
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4909ZPiper PA-22
Status
Completed · report May 17, 1966
Report
Brief approved by the director
Case key
172599

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-0741  66/4/16    ONTONAGON MICH      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 224
        TIME - 1700                    N4909Z              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 66 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SCHUSTER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY

Aircraft

Registration
N4909Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Schuster

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.