SEA66D0236

NTSB accident investigation · Stinson 6A · Burley, ID · March 26, 1966

Accident · No injuriesClosed
Date
March 26, 1966
Place
Burley, ID · BURLEY, ID
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9718KStinson 6A
Status
Completed · report May 5, 1966
Report
Brief approved by the director
Case key
173201

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-0597  66/3/26    BURLEY ID           STINSON 6A          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 48, 151
        TIME - 1900                    N9718K              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 3 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BURLEY
        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
N9718K
Reported as
Stinson 6A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Burley

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.