SEA66A0001

NTSB accident investigation · Emigh Trojan · Vacaville, CA · July 1, 1965

Accident · FatalClosed
Date
July 1, 1965
Place
Vacaville, CA · VACAVILLE, CA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Landing
Aircraft
N8321HEmigh Trojan
Status
Completed · report December 21, 1965
Report
Brief approved by the director
Case key
177307

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-0727   65/7/1  NR.VACAVILLE CALIF    EMIGH TROJAN        CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 24, 300
        TIME - 2100                    N8321H              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 16 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        MISSING AIRCRAFT - LATER RECOVERED
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
                                  UNKNOWN/NOT REPORTED
         FIRE AFTER IMPACT
        REMARKS- RECOVERY DATE 7-2-65.

Aircraft

Registration
N8321H
Reported as
Emigh Trojan
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.