UNK64X1074

NTSB accident investigation · Piper PA28 · Bloomington, IN · March 28, 1964

Accident · No injuriesClosed
Date
March 28, 1964
Place
Bloomington, IN · BLOOMINGTON, IN
Injuries
5 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7291WPiper PA28
Status
Completed · report September 9, 1964
Report
Brief approved by the director
Case key
184535

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-0732  64/3/28    BLOOMINGTON IND     PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 96 TOTAL
        TIME - 1100                    N7291W              PX-  0  0  4  PLEASURE/PERSONAL TRANSP  HOURS, 40 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - WET,SOFT GROUND
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT

Aircraft

Registration
N7291W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.