NYC67D0673

NTSB accident investigation · Piper PA-28 · Lockhaven, PA · May 13, 1967

Accident · No injuriesClosed
Date
May 13, 1967
Place
Lockhaven, PA · LOCKHAVEN, PA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N6506WPiper PA-28
Status
Completed · report September 11, 1967
Report
Brief approved by the director
Case key
117218

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-1496  67/5/13    LOCKHAVEN, PA       PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 22, 221
        TIME - 1530                    N6506W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 40 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- POWER LINE 33 FT ABOVE RIVER. ACFT CONTINUED FLIGHT, LANDED SAFELY.

Aircraft

Registration
N6506W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.