MKC67D0462

NTSB accident investigation · Piper PA-22 · Sac City, IA · February 26, 1967

Accident · No injuriesClosed
Date
February 26, 1967
Place
Sac City, IA · SAC CITY, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3533ZPiper PA-22
Status
Completed · report August 11, 1967
Report
Brief approved by the director
Case key
118439

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-0628  67/2/26    SAC CITY,IOWA       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 25, 185
        TIME - 2015                    N3533Z              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 31 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SAC CITY MUNI
        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
N3533Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sac City Muni

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.