MKC68F0292

NTSB accident investigation · Piper PA-22 · New Town, ND · October 3, 1967

Accident · No injuriesClosed
Date
October 3, 1967
Place
New Town, ND · NEW TOWN, ND
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3560APiper PA-22
Status
Completed · report December 27, 1967
Report
Brief approved by the director
Case key
113840

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-3579   67/10/3   NEW TOWN,N DAK      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 115
        TIME - 1900                    N3560A              PX-  0  0  2  BUSINESS                  TOTAL HOURS, 49 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NEW TOWN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3560A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
New Town

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.