- Date
- August 1, 1965
- Place
- Woodville, OH · WOODVILLE, OH
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N8636ABeechcraft A35
- Status
- Completed · report December 10, 1965
- Report
- Brief approved by the director
- Case key
- 177290
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-0678 65/8/1 WOODVILLE OHIO BEECHCRAFT A35 CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, AGE 44, 2000 TIME - 1734 N8636A PX- 3 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - HAAR TYPE OF ACCIDENT PHASE OF OPERATION AIRFRAME FAILURE: IN FLIGHT IN FLIGHT: OTHER 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 - CONTINUED FLIGHT INTO KNOWN AREAS OF SEVERE TURBULENCE MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE FACTOR(S) WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS WEATHER BRIEFING - BRIEFED BY WEATHER BUREAU PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS THUNDERSTORM TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE REMARKS- AIRCRAFT ENTERED THUNDERSTORM.
Aircraft
- Registration
- N8636A
- Reported as
- Beechcraft A35
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Haar
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.