MIA66A0104

NTSB accident investigation · Piper J3C-65 · Central Falls, NC · March 13, 1966

Accident · FatalClosed
Date
March 13, 1966
Place
Central Falls, NC · CENTRAL FALLS, NC
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N70434Piper J3C-65
Status
Completed · report August 1, 1966
Report
Brief approved by the director
Case key
174134

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-0148  66/3/13    CENTRAL FALLS NC    PIPER J3C-65        CR-  1  0  0  NONCOMMERCIAL             STUDENT, AGE 53, UNK/NR
        TIME - 1615                    N70434              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - FAGG AIRSTRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE
         FIRE AFTER IMPACT

Aircraft

Registration
N70434
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Fagg Airstrip

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.