MIA66D0396

NTSB accident investigation · Piper PA-23 · Haleyville, AL · November 22, 1965

Accident · No injuriesClosed
Date
November 22, 1965
Place
Haleyville, AL · HALEYVILLE, AL
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4926FPiper PA-23
Status
Completed · report April 11, 1966
Report
Brief approved by the director
Case key
174412

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-3919  65/11/22   HALEYVILLE ALA      PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 677
        TIME - 2030                    N4926F              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 67 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HALEYVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N4926F
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Haleyville

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.