NYC67A0099

NTSB accident investigation · Piper PA-28 · Plattsburgh, NY · January 8, 1967

Accident · No injuriesClosed
Date
January 8, 1967
Place
Plattsburgh, NY · PLATTSBURGH, NY
Injuries
1 uninjured
Damage
Minor damage
Phase of flight
Standing
Aircraft
N9293JPiper PA-28
Status
Completed · report June 27, 1967
Report
Brief approved by the director
Case key
119501

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
----------------------------------------------------------------------------------------------------------------------------
2-0068   67/1/8    PLATTSBURGH,NY      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 31, 317
        TIME - 1530                    N9293J              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 77 IN TYPE,
                                       DAMAGE-MINOR        OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PLATTSBURGH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           PROPELLER/ROTOR ACCIDENT TO PERSON                       STATIC: IDLING ENGINE(S)
        PROBABLE CAUSE(S)
           PERSONNEL - MISCELLANEOUS-PERSONNEL: PASSENGER
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
        REMARKS- RAMP ICY.PLT DID NOT STOP ENG FOR PAX TO DEPLANE.PAX STRUCK BY ROTATING PROPELLER WHILE DEPLANING.

Aircraft

Registration
N9293J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Minor damage
Airport
Plattsburgh

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.