MIA67A0119

NTSB accident investigation · Piper PA-28 · Somerville, TN · May 9, 1967

Accident · FatalClosed
Date
May 9, 1967
Place
Somerville, TN · SOMERVILLE, TN
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N4347JPiper PA-28
Status
Completed · report September 8, 1967
Report
Brief approved by the director
Case key
117835

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-0355   67/5/9    SOMERVILLE,TENN     PIPER PA-28         CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 25, 275
        TIME - 1007                    N4347J              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OZIER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: BUZZING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        REMARKS- 60FT HI PARALLELING PWR LINES LOCATED APPROXIMATELY 1200 FT WEST OF RNWY 15. ACFT HEADING 100 DEGS

Aircraft

Registration
N4347J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Ozier

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.