CHI73DEA20

NTSB accident investigation · Piper PA-32 · Muncie, IN · November 5, 1972

Accident · Serious injuriesClosed
Date
November 5, 1972
Place
Muncie, IN · MUNCIE, IN
Injuries
1 serious, 3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5588JPiper PA-32
Status
Completed · report December 19, 1972
Report
Brief approved by the director
Case key
168619

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-0825   72/11/5   MUNCIE,IND          PIPER PA-32         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 46, 3227
        TIME - 1038                    N5588J              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 542 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MUNCIE MUNI
        DEPARTURE POINT             INTENDED DESTINATION
          MUNCIE,IND                  LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        REMARKS- BOTH WING SPARS BENT.

Aircraft

Registration
N5588J
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Muncie Muni

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.