MIA65A0088

NTSB accident investigation · Piper J3C · Atmore, AL · February 28, 1965

Accident · FatalClosed
Date
February 28, 1965
Place
Atmore, AL · ATMORE, AL
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N70262Piper J3C
Status
Completed · report July 2, 1965
Report
Brief approved by the director
Case key
179259

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-0232  65/2/28  NR.ATMORE ALA         PIPER J3C           CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 31, 200
        TIME - 1630                    N70262              PX-  1  0  0  PRACTICE                  TOTAL HOURS, 97 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: ACROBATICS
           STALL: SPIN                                              IN FLIGHT: ACROBATICS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE

Aircraft

Registration
N70262
Reported as
Piper J3C
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.