UNK64X0281

NTSB accident investigation · Piper PA22 · Burlington, NC · January 18, 1964

Accident · No injuriesClosed
Date
January 18, 1964
Place
Burlington, NC · BURLINGTON, NC
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N3005ZPiper PA22
Status
Completed
Report
Brief approved by the director
Case key
185536

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-0141  64/1/18    BURLINGTON NC       PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 130
        TIME - 1600                    N3005Z              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF POWERPLANT & POWERPLANT CONTROLS
           MISCELLANEOUS ACTS,CONDITIONS - ICE-CARBURETOR
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N3005Z
Reported as
Piper PA22
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.