MIA70A0011

NTSB accident investigation · Piper J-3 · Lafayette, TN · August 1, 1969

Accident · FatalClosed
Date
August 1, 1969
Place
Lafayette, TN · LAFAYETTE, TN
Injuries
1 fatal, 1 uninjured
Damage
No damage
Phase of flight
Standing
Aircraft
N70223Piper J-3
Status
Completed · report February 27, 1970
Report
Brief approved by the director
Case key
166408

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-3110   69/8/1    LAFAYETTE,TENN      PIPER J-3           CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 45, 800
        TIME - 1850                    N70223              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 60 IN TYPE,
                                       DAMAGE-NONE         OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GALLATIN
        DEPARTURE POINT             INTENDED DESTINATION
          LAFAYETTE,TENN              LAFAYETTE,TENN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           PROPELLER/ROTOR ACCIDENT TO PERSON                       STATIC: IDLING ENGINE(S)
        PROBABLE CAUSE(S)
           PERSONNEL - MISCELLANEOUS-PERSONNEL: PASSENGER
        REMARKS- PX BLOOD ALCOHOL LEVEL 0.13 PCT.DEPLANING PX WALKED INTO PROP.

Aircraft

Registration
N70223
Reported as
Piper J-3
Category
Airplane
Engine
reciprocating
Damage
No damage
Airport
Gallatin

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.