LAX69A0005

NTSB accident investigation · Beech A35 · Phoenix, AZ · July 8, 1968

Accident · FatalClosed
Date
July 8, 1968
Place
Phoenix, AZ · PHOENIX, AZ
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8450ABeech A35
Status
Completed · report November 5, 1968
Report
Brief approved by the director
Case key
109537

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-3180   68/7/8    PHOENIX,ARIZ        BEECH A35           CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 37, 1500
        TIME - 0802                    N8450A              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 700 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PHOENIX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           TURBULENCE                                               LANDING: FINAL APPROACH
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - VORTEX TURBULENCE
           PILOT IN COMMAND - MISJUDGED DISTANCE
         FIRE AFTER IMPACT
        REMARKS- LNDG BEHIND LARGE JET.

Aircraft

Registration
N8450A
Reported as
Beech A35
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Phoenix

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.