DIA69D0027

NTSB accident investigation · Piper PA-32 · Ravenswood, WV · May 30, 1968

Accident · No injuriesClosed
Date
May 30, 1968
Place
Ravenswood, WV · RAVENSWOOD, WV
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3854WPiper PA-32
Status
Completed · report August 16, 1968
Report
Brief approved by the director
Case key
109815

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-1933  68/5/30    RAVENSWOOD,W VA     PIPER PA-32         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 57, 3000
        TIME - 0900                    N3854W              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 40 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - RAVENSWOOD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT
                                  SUSPECTED OR KNOWN AIRCRAFT DAMAGE
        REMARKS- LANDED ON ROAD NO FURTHER DAMAGE

Aircraft

Registration
N3854W
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ravenswood

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.