CHI67D0028

NTSB accident investigation · Piper PA-24 · Indianapolis, IN · May 21, 1966

Accident · No injuriesClosed
Date
May 21, 1966
Place
Indianapolis, IN · INDIANAPOLIS, IN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5044PPiper PA-24
Status
Completed · report August 9, 1966
Report
Brief approved by the director
Case key
171794

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-1420  66/5/21    INDIANAPOLIS IND    PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 851
        TIME - 1150                    N5044P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BOB SHANK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N5044P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bob Shank

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.