NYC68F0209

NTSB accident investigation · Piper J3C-65 · Mashpee, MA · August 24, 1967

Accident · No injuriesClosed
Date
August 24, 1967
Place
Mashpee, MA · MASHPEE, MA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N6362HPiper J3C-65
Status
Completed · report December 14, 1967
Report
Brief approved by the director
Case key
114337

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-3377  67/8/24  NR.MASHPEE,MASS       PIPER J3C-65        CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 16, 27 TOTAL
        TIME - 1630                    N6362H              PX-  0  0  0  TRAINING                  HOURS, 8 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           COLLIDED WITH: TREES                                     LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N6362H
Reported as
Piper J3C-65
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.