CHI69F0344

NTSB accident investigation · Piper PA-22 · Darby Dale, OH · November 8, 1968

Accident · Serious injuriesClosed
Date
November 8, 1968
Place
Darby Dale, OH · DARBY DALE, OH
Injuries
1 serious, 2 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8895CPiper PA-22
Status
Completed · report January 31, 1969
Report
Brief approved by the director
Case key
107628

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-4228   68/11/8   DARBY DALE,OHIO     PIPER PA-22         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 30, 190
        TIME - 1827                    N8895C              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 75 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DARBY DALE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- ATTEMPTED LNDG ON UNLIGHTED STRIP. FOURTH ATTEMPT.

Aircraft

Registration
N8895C
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Darby Dale

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.