NYC66D0511

NTSB accident investigation · Piper PA-22 · Moorestown, NJ · February 7, 1966

Accident · No injuriesClosed
Date
February 7, 1966
Place
Moorestown, NJ · MOORESTOWN, NJ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3340ZPiper PA-22
Status
Completed · report March 28, 1966
Report
Brief approved by the director
Case key
173810

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-0268   66/2/7    MOORESTOWN NJ       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 35, 51 TOTAL
        TIME - 1900                    N3340Z              PX-  0  0  0  PRACTICE                  HOURS, 38 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA
        FACTOR(S)
           PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL
        REMARKS- NIGHT OPERATION ON LIGHTED AIRPORT. AIRCRAFT WAS LANDED OFF RUNWAY IN DEEP SNOW.

Aircraft

Registration
N3340Z
Reported as
Piper PA-22
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.