UNK64X0663

NTSB accident investigation · Piper J3C · Garland, KS · February 22, 1964

Accident · Minor injuriesClosed
Date
February 22, 1964
Place
Garland, KS · GARLAND, KS
Injuries
2 minor
Damage
Destroyed
Phase of flight
Approach
Aircraft
N3557NPiper J3C
Status
Completed
Report
Brief approved by the director
Case key
185242

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-0446  64/2/22    GARLAND KANS        PIPER J3C           CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 42, 71 TOTAL
        TIME - 1800                    N3557N              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            LANDING: GO-AROUND
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF POWERPLANT & POWERPLANT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - ANTI-ICING/DEICING EQUIPMENT-IMPROPER OPERATION OF/OR FAILED TO USE
        REMARKS- CARBURETOR HEAT ON DURING GO-AROUND.

Aircraft

Registration
N3557N
Reported as
Piper J3C
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.