LAX66A0066

NTSB accident investigation · Piper J5A · Mc Farland, CA · March 6, 1966

Accident · FatalClosed
Date
March 6, 1966
Place
Mc Farland, CA · MC FARLAND, CA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N54460Piper J5A
Status
Completed · report August 1, 1966
Report
Brief approved by the director
Case key
174133

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-0147   66/3/6  NR.MC FARLAND CALIF   PIPER J5A           CR-  1  0  0  NONCOMMERCIAL             STUDENT, AGE 23, 72 TOTAL
        TIME - 1715                    N54460              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 70 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - POSO-KERN COUNTY
        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
           MISCELLANEOUS ACTS,CONDITIONS - ALCOHOLIC IMPAIRMENT OF EFFICIENCY AND JUDGMENT

Aircraft

Registration
N54460
Reported as
Piper J5A
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Poso-Kern County

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.