- Date
- April 23, 1972
- Place
- Orinda, CA · ORINDA, CA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N3732FCessna 172H
- Status
- Completed · report November 27, 1972
- Report
- Brief approved by the director
- Case key
- 165790
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-0704 72/4/23 ORINDA,CALIF CESSNA 172H CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 26, 88 TOTAL TIME - 2226 N3732F PX- 0 0 0 PLEASURE/PERSONAL TRANSP HOURS, UNK/NR IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LIVERMORE,CALIF NAPA,CALIF TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST/LOWER SCATTERED 2800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES NONE 220 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 15 VFR TYPE OF FLIGHT PLAN NONE REMARKS- CONT FLT INTO KNOWN MARGINAL WEA. LOST CTL.
Aircraft
- Registration
- N3732F
- Reported as
- Cessna 172H
- 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.