FTW70F0087

NTSB accident investigation · Aeronca 65-CA · Huntsville, TX · June 15, 1969

Accident · No injuriesClosed
Date
June 15, 1969
Place
Huntsville, TX · HUNTSVILLE, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N33875Aeronca 65-CA
Status
Completed · report September 10, 1969
Report
Brief approved by the director
Case key
179523

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-2218  69/6/15    HUNTSVILLE,TEX      AERONCA 65-CA       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 94 TOTAL
        TIME - 1900                    N33875              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 2 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HUNTSVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N33875
Reported as
Aeronca 65-CA
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Huntsville

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.