NYC69D0314

NTSB accident investigation · Piper PA-23 · Pittsfield, ME · February 6, 1969

Accident · No injuriesClosed
Date
February 6, 1969
Place
Pittsfield, ME · PITTSFIELD, ME
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6370YPiper PA-23
Status
Completed · report May 1, 1969
Report
Brief approved by the director
Case key
191652

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-0228   69/2/6    PITTSFIELD,ME       PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 38, 1500
        TIME - 1830                    N6370Y              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 410 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PITTSFIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: SNOWBANK                                  LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: ICE/SLUSH ON RUNWAY

Aircraft

Registration
N6370Y
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pittsfield

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.