- Date
- October 10, 1969
- Place
- Carson City, NV · CARSON CITY, NV
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N7693NBeech E33
- Status
- Completed · report August 5, 1970
- Report
- Brief approved by the director
- Case key
- 155038
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-3774 69/10/10 NR.CARSON CITY,NEV BEECH E33 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 32, 136 TIME - 2210 N7693N PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 65 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAKE TAHOE,CALIF RENO,NEV TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING WEATHER - DOWNDRAFT,UPDRAFTS FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES NONE 80 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 51 VFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- SIGMET VALID FOR MDT TO SEVERE TURB IN AREA. ACFT CRASHED INTO MNTN SLOPE.
Aircraft
- Registration
- N7693N
- Reported as
- Beech E33
- 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.