LAX70AL060

NTSB accident investigation · Amer Avco AA-1 · Mt Baldy, CA · March 21, 1970

Accident · FatalClosed
Date
March 21, 1970
Place
Mt Baldy, CA · MT BALDY, CA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N5994LAmer Avco AA-1
Status
Completed · report December 28, 1970
Report
Brief approved by the director
Case key
134507

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-1484  70/3/21    MT BALDY,CALIF      AMER AVCO AA-1      CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 31, 400
        TIME - 1520                    N5994L              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          FULLERTON,CALIF             LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
         FIRE AFTER IMPACT
        REMARKS- INVESTIGATION REVEALED ACFT IN NR VER DIVE AT IMPACT.ACFT CONSUMED BY FIRE.1.5HRS CK OUT BFR FLT.

Aircraft

Registration
N5994L
Reported as
Amer Avco AA-1
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.