UNK64X0764

NTSB accident investigation · Piper PA22 · Birmingham, MI · February 29, 1964

Accident · FatalClosed
Date
February 29, 1964
Place
Birmingham, MI · BIRMINGHAM, MI
Injuries
1 fatal, 2 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N5608PPiper PA22
Status
Completed · report January 28, 1965
Report
Brief approved by the director
Case key
185785

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-0154  64/2/29    BIRMINGHAM MICH     PIPER PA22          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 58, 376
        TIME - 1200                    N5608P              PX-  1  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 170 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BERZ
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            TAKEOFF: INITIAL CLIMB
           STALL                                                    TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N5608P
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Berz

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.