- Date
- October 8, 1972
- Place
- Acton, CA · ACTON, CA
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N35803Cessna 172I
- Status
- Completed · report March 13, 1973
- Report
- Brief approved by the director
- Case key
- 169019
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-3187 72/10/8 ACTON,CALIF CESSNA 172I CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 19, 80 TOTAL TIME - 1745 N35803 PX- 3 0 0 PLEASURE/PERSONAL TRANSP HOURS, 15 IN TYPE, NOT DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - AGUA DULCE DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP LAS VEGAS,NEV VAN NUYS,CALIF LANCASTER,CALIF TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION UNKNOWN/NOT REPORTED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/2 MILE OR LESS DRIZZLE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN VFR REMARKS- OBS IN LOW FLT OVER FREEWAY.THEN TURNED L INTO CLDS. HIT SMALL TREE AND SLID INTO HOUSE.
Aircraft
- Registration
- N35803
- Reported as
- Cessna 172I
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Agua Dulce
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.