CHI68A0024

NTSB accident investigation · Piper PA-30 · Crawfordsvle, IN · September 6, 1967

Accident · FatalClosed
Date
September 6, 1967
Place
Crawfordsvle, IN · CRAWFORDSVLE, IN
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N8411YPiper PA-30
Status
Completed · report February 12, 1968
Report
Brief approved by the director
Case key
114546

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-0928   67/9/6    CRAWFORDSVLE,IND    PIPER PA-30         CR-  2  0  0  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 0915                    N8411Y              PX-  0  0  0  DUAL                      AGE 42, 1471 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            43 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
         FIRE AFTER IMPACT
        REMARKS- STUDENT TRAINING FOR MULTI-ENG RATING,NO PRIOR MULTI-ENG EXPERIENCE.

Aircraft

Registration
N8411Y
Reported as
Piper PA-30
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.