- Date
- April 23, 1972
- Place
- Olancha, CA · OLANCHA, CA
- Injuries
- 1 minor, 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N3832SCessna 172
- Status
- Completed · report February 7, 1973
- Report
- Brief approved by the director
- Case key
- 166047
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-1793 72/4/23 OLANCHA,CALIF CESSNA 172 CR- 0 0 2 NONCOMMERCIAL PRIVATE, AGE 44, 426 TIME - 1400 N3832S PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 380 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - USFS MONACHE STRP DEPARTURE POINT INTENDED DESTINATION OLANCHA,CALIF SAN JOSE,CALIF TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: FENCE,FENCEPOSTS TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT WEATHER - HIGH DENSITY ALTITUDE FACTOR(S) TERRAIN - WET,SOFT GROUND WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED 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 TEMPERATURE-F NONE 58 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- DENS ALT ABT 10000FT,UN CLMB AFTR TKOF.UN TURN AROUND AFTR HITTING FENCE,CRASH LNDD,NOSED OVR.
Aircraft
- Registration
- N3832S
- Reported as
- Cessna 172
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Usfs Monache Strp
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.