CHI66D0701

NTSB accident investigation · Piper PA-28 · Cambridge Cty, IN · April 8, 1966

Accident · No injuriesClosed
Date
April 8, 1966
Place
Cambridge Cty, IN · CAMBRIDGE CTY, IN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5783WPiper PA-28
Status
Completed · report June 8, 1966
Report
Brief approved by the director
Case key
172642

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-0820   66/4/8    CAMBRIDGE CTY IND   PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 39, 33 TOTAL
        TIME - 1600                    N5783W              PX-  0  0  0  PRACTICE                  HOURS, 8 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
        REMARKS- OFF AIRPORT OPERATION ON ROAD

Aircraft

Registration
N5783W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.