NYC69A0007

NTSB accident investigation · Piper PA-30 · Lock Haven, PA · July 9, 1968

Accident · FatalClosed
Date
July 9, 1968
Place
Lock Haven, PA · LOCK HAVEN, PA
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8572YPiper PA-30
Status
Completed · report October 2, 1968
Report
Brief approved by the director
Case key
109466

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-2399   68/7/9    LOCK HAVEN,PA       PIPER PA-30         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 55, 555
        TIME - 1620                    N8572Y              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 330 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LOCK HAVEN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    LANDING: TRAFFIC PATTERN-CIRCLING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - POORLY PLANNED APPROACH
         FIRE AFTER IMPACT
        REMARKS- IN STEEP BANK,TURNING TO FINAL.

Aircraft

Registration
N8572Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Lock Haven

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.