DIA68F0131

NTSB accident investigation · Piper PA-22 · Odenton, MD · November 26, 1967

Accident · No injuriesClosed
Date
November 26, 1967
Place
Odenton, MD · ODENTON, MD
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5974ZPiper PA-22
Status
Completed · report January 23, 1968
Report
Brief approved by the director
Case key
112878

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-4136  67/11/26   ODENTON,MD          PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 42, 27 TOTAL
        TIME - 1355                    N5974Z              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - TIPTON AAF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5974Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Tipton Aaf

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.