MIA65F0106

NTSB accident investigation · Piper J3C · Louisburg, NC · May 21, 1965

Accident · Serious injuriesClosed
Date
May 21, 1965
Place
Louisburg, NC · LOUISBURG, NC
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N30226Piper J3C
Status
Completed · report August 13, 1965
Report
Brief approved by the director
Case key
178050

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
----------------------------------------------------------------------------------------------------------------------------
2-0297  65/5/21    LOUISBURG NC        PIPER J3C           CR-  0  1  0  NONCOMMERCIAL             STUDENT, AGE 27, 45 TOTAL
        TIME - 1830                    N30226              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FRANKLIN FIELD
        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
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER

Aircraft

Registration
N30226
Reported as
Piper J3C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Franklin Field

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.