NYC66F0233

NTSB accident investigation · Piper PA15 · Bloomsburg, PA · August 30, 1965

Accident · Serious injuriesClosed
Date
August 30, 1965
Place
Bloomsburg, PA · BLOOMSBURG, PA
Injuries
2 serious
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N4132HPiper PA15
Status
Completed · report October 22, 1965
Report
Brief approved by the director
Case key
176315

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-0516  65/8/30    BLOOMSBURG PA       PIPER PA15          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 42, 558
        TIME - 1645                    N4132H              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 74 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        REMARKS- PILOT TAKING PICTURES AT TREE TOP HEIGHT

Aircraft

Registration
N4132H
Reported as
Piper PA15
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.