DEN66D0259

NTSB accident investigation · Stinson 108 · Buckeye, AZ · March 17, 1966

AccidentClosed
Date
March 17, 1966
Place
Buckeye, AZ · BUCKEYE, AZ
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9147KStinson 108
Status
Completed · report April 28, 1966
Report
Brief approved by the director
Case key
173164

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-0555  66/3/17    BUCKEYE ARIZ        STINSON 108         CR-  0  0  0  MISCELLANEOUS             AGE Z , UNK/NR TOTAL
        TIME - UNK/NR                  N9147K              PX-  0  0  0  UNKNOWN/NOT REPORTED      HOURS, UNK/NR IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            UNK/NR INSTRUMENT RATED.
        NAME OF AIRPORT - BUCKEYE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - STOLEN OR UNAUTH=
        REMARKS- PILOT COULD NOT BE LOCATED, INJURIES UNKNOWN.

Aircraft

Registration
N9147K
Reported as
Stinson 108
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Buckeye

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.