UNK64X2780

NTSB accident investigation · Piper PA11 · Sullivan, IN · July 12, 1964

Accident · Serious injuriesClosed
Date
July 12, 1964
Place
Sullivan, IN · SULLIVAN, IN
Injuries
2 serious, 1 minor
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N4767MPiper PA11
Status
Completed · report October 30, 1964
Report
Brief approved by the director
Case key
183589

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-0384  64/7/12    SULLIVAN IND        PIPER PA11          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 59, 500
        TIME - 1630                    N4767M              PX-  0  1  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 475 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           MISCELLANEOUS ACTS,CONDITIONS - IMPROPERLY LOADED AIRCRAFT-WEIGHT-AND/OR C.G.
        REMARKS- 0NE PASSENGER WAS AN INFANT

Aircraft

Registration
N4767M
Reported as
Piper PA11
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.