UNK65X0121

NTSB accident investigation · Aeronca L16A · Jefferson, OH · October 3, 1964

Accident · Minor injuriesClosed
Date
October 3, 1964
Place
Jefferson, OH · JEFFERSON, OH
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9653HAeronca L16A
Status
Completed · report November 17, 1964
Report
Brief approved by the director
Case key
181369

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-3097   64/10/3   JEFFERSON OHIO      AERONCA L16A        CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 25, 122
        TIME - 1505                    N9653H              PX-  0  0  1  PRACTICE                  TOTAL HOURS, 13 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JEFFERSON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: GO-AROUND
           COLLIDED WITH: OBJECT                                    LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        REMARKS- AIRCRAFT COLLIDED WITH HIGH WEEDS OFF RUNWAY.

Aircraft

Registration
N9653H
Reported as
Aeronca L16A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Jefferson

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.