UNK65X1343

NTSB accident investigation · Piper PA-18 · Tustin, WI · January 24, 1965

Accident · Serious injuriesClosed
Date
January 24, 1965
Place
Tustin, WI · TUSTIN, WI
Injuries
2 serious
Damage
Destroyed
Phase of flight
Approach
Aircraft
N1021APiper PA-18
Status
Completed · report March 25, 1965
Report
Brief approved by the director
Case key
180474

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
----------------------------------------------------------------------------------------------------------------------------
2-0029  65/1/24    TUSTIN WIS          PIPER PA-18         CR-  0  1  0  NONCOMMERCIAL             STUDENT, AGE 34, 191
        TIME - 1030                    N1021A              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 135 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           MISCELLANEOUS ACTS,CONDITIONS - AIRFRAME ICE
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        REMARKS- LANDING ON FROZEN LAKE-PILOT FAILED TO REMOVE ALL ICE FROM WINGS DURING PREFLIGHT

Aircraft

Registration
N1021A
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.