UNK64X3174

NTSB accident investigation · Stinson 108 · Ashfork, AZ · August 2, 1964

Accident · No injuriesClosed
Date
August 2, 1964
Place
Ashfork, AZ · ASHFORK, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N97623Stinson 108
Status
Completed · report October 20, 1964
Report
Brief approved by the director
Case key
182274

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-2309   64/8/2    ASHFORK ARIZ        STINSON 108         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 60, 506
        TIME - 0930                    N97623              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ASH FORK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.

Aircraft

Registration
N97623
Reported as
Stinson 108
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ash Fork

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.