UNK64X3186

NTSB accident investigation · Piper PA-22 · Bloomsburg, PA · August 2, 1964

Accident · FatalClosed
Date
August 2, 1964
Place
Bloomsburg, PA · BLOOMSBURG, PA
Injuries
2 fatal, 2 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N8109DPiper PA-22
Status
Completed · report January 6, 1965
Report
Brief approved by the director
Case key
182668

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-0661   64/8/2    BLOOMSBURG PA       PIPER PA-22         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 41, 211
        TIME - 1405                    N8109D              PX-  1  2  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 92 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - IMPROPERLY LOADED AIRCRAFT-WEIGHT-AND/OR C.G.
         FIRE AFTER IMPACT

Aircraft

Registration
N8109D
Reported as
Piper PA-22
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.