- Date
- September 30, 1965
- Place
- White Cloud, MI · WHITE CLOUD, MI
- Injuries
- 3 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N8413UCessna 172
- Status
- Completed · report February 25, 1966
- Report
- Brief approved by the director
- Case key
- 175902
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-1071 65/9/30 NR.WHITE CLOUD MICH. CESSNA 172 CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0025 N8413U PX- 2 0 0 PLEASURE/PERSONAL TRANSP AGE 39, 2000 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 25 IN TYPE, NOT INSTRUMENT RATED. 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 PERSONNEL - WEATHER PERSONNEL: INADEQUATE/INCORRECT WEATHER BRIEFING FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY WEATHER BUREAU PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO DRIZZLE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 57 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 120 7 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR SPECIAL VFR REMARKS- RECOVERY DATE 10/1/65.
Aircraft
- Registration
- N8413U
- Reported as
- Cessna 172
- 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.