CHI69F0547

NTSB accident investigation · Piper PA-22 · Phillipsburg, OH · March 23, 1969

Accident · Serious injuriesClosed
Date
March 23, 1969
Place
Phillipsburg, OH · PHILLIPSBURG, OH
Injuries
1 serious, 1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N7036BPiper PA-22
Status
Completed · report May 22, 1969
Report
Brief approved by the director
Case key
190915

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-0550  69/3/23    PHILLIPSBURG,OHIO   PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 56, 1400
        TIME - 1600                    N7036B              PX-  0  1  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 40 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MYERS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           PILOT IN COMMAND - IMPROPER COMPENSATION FOR WIND CONDITIONS
        REMARKS- LFT QUARTERING HEAD WIND 30 DEG 6K.

Aircraft

Registration
N7036B
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Myers

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.