- Date
- June 6, 1968
- Place
- Cleveland, ND · CLEVELAND, ND
- Injuries
- 2 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N8307ZCessna 210-5
- Status
- Completed · report August 8, 1968
- Report
- Brief approved by the director
- Case key
- 110356
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-1813 68/6/6 CLEVELAND,N DAK CESSNA 210-5 CR- 0 1 0 NONCOMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0120 N8307Z PX- 0 1 0 BUSINESS AGE 27, UNK/NR TOTAL DAMAGE-DESTROYED OT- 0 0 0 HOURS, UNK/NR IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - RAU TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED 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 BRIEFING - BRIEFED BY WEATHER BUREAU PERSONEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 400 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) RAIN SHOWERS OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 60 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 340 9 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR SPECIAL VFR REMARKS- PLT ATTEMPTED TO MAINTAIN VISUAL REFERENCE AT NIGHT. AREA SPARSELY POPULATED. FLEW INTO HILLSIDE.
Aircraft
- Registration
- N8307Z
- Reported as
- Cessna 210-5
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Rau
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.