DIA68A0050

NTSB accident investigation · Piper PA-30 · New Mrtnsvil, WV · May 27, 1968

Accident · FatalClosed
Date
May 27, 1968
Place
New Mrtnsvil, WV · NEW MRTNSVIL, WV
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N7996YPiper PA-30
Status
Completed · report August 5, 1968
Report
Brief approved by the director
Case key
110322

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-1752  68/5/27    NEW MRTNSVIL,W VA   PIPER PA-30         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 46, 3020
        TIME - 2025                    N7996Y              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 1246 IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - NEW MARTINSVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PILOT MADE A SHORT FIELD TAKE OFF FROM WET SOD RUNWAY AT NIGHT

Aircraft

Registration
N7996Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
New Martinsville

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.