LAX67F0105

NTSB accident investigation · Cessna 150 · Adamana, AZ · September 7, 1966

Accident · Serious injuriesClosed
Date
September 7, 1966
Place
Adamana, AZ · ADAMANA, AZ
Injuries
1 serious
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N3680JCessna 150
Status
Completed · report August 29, 1967
Report
Brief approved by the director
Case key
121027

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
----------------------------------------------------------------------------------------------------------------------------
2-1197   66/9/7    ADAMANA,ARIZ        CESSNA 150          CR-  0  1  0  MISCELLANEOUS             PRIVATE, AGE 26, 127
        TIME - 0822                    N3680J              PX-  0  0  0  FERRY                     TOTAL HOURS, 18 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N3680J
Reported as
Cessna 150
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.