NYC65F0053

NTSB accident investigation · Piper PA28 · Newport, VT · February 13, 1965

Accident · No injuriesClosed
Date
February 13, 1965
Place
Newport, VT · NEWPORT, VT
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8004WPiper PA28
Status
Completed · report March 26, 1965
Report
Brief approved by the director
Case key
180165

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-0279  65/2/13    NEWPORT VT          PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 150
        TIME - 1700                    N8004W              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 35 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NEWPORT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: SNOWBANK                                  TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: ICE/SLUSH ON RUNWAY

Aircraft

Registration
N8004W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Newport

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.