DEN66F0105

NTSB accident investigation · Piper PA-23 · Evanston, WY · September 16, 1965

Accident · No injuriesClosed
Date
September 16, 1965
Place
Evanston, WY · EVANSTON, WY
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1096PPiper PA-23
Status
Completed · report October 21, 1965
Report
Brief approved by the director
Case key
176088

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-2617  65/9/16    EVANSTON WYO        PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 24, 802
        TIME - 1615                    N1096P              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 40 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - EVANSTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: DIRT BANK                                 LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N1096P
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Evanston

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.