UNK64X1694

NTSB accident investigation · Piper J3 · Minneapolis, MN · May 10, 1964

Accident · No injuriesClosed
Date
May 10, 1964
Place
Minneapolis, MN · MINNEAPOLIS, MN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N33023Piper J3
Status
Completed · report September 18, 1964
Report
Brief approved by the director
Case key
183884

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-1226  64/5/10    MINNEAPOLIS MINN    PIPER J3            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 3000
        TIME - 0900                    N33023              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1000 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - CRYSTAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - PREMATURE LIFT-OFF
        REMARKS- FLOAT PLANE TAKEOFF USING A DOLLY

Aircraft

Registration
N33023
Reported as
Piper J3
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Crystal

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.