MIA67D0131

NTSB accident investigation · Piper PA-22 · Johns Island, SC · July 2, 1966

Accident · No injuriesClosed
Date
July 2, 1966
Place
Johns Island, SC · JOHNS ISLAND, SC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N3164ZPiper PA-22
Status
Completed · report October 4, 1966
Report
Brief approved by the director
Case key
171001

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-2082   66/7/2    JOHNS ISLAND SC     PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 37, 66 TOTAL
        TIME - 1345                    N3164Z              PX-  0  0  0  PRACTICE                  HOURS, 26 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - JOHN ISLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SIMULATED CONDITIONS
        REMARKS- PILOT WAS PRACTISING FORCED LANDINGS.

Aircraft

Registration
N3164Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
John Island

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.