SEA68F0182

NTSB accident investigation · Bellanca 14-13 · Aurora, OR · August 28, 1967

Accident · No injuriesClosed
Date
August 28, 1967
Place
Aurora, OR · AURORA, OR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N74325Bellanca 14-13
Status
Completed · report February 14, 1968
Report
Brief approved by the director
Case key
114008

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-4494  67/8/28    AURORA,OREG         BELLANCA 14-13      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 222
        TIME - 1730                    N74325              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 126 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - AURORA
        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
N74325
Reported as
Bellanca 14-13
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Aurora

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.