- Date
- March 30, 1973
- Place
- Hanover, MI · HANOVER, MI
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N3506BBeech E35
- Status
- Completed · report May 24, 1973
- Report
- Brief approved by the director
- FAA report
- 19730330009289A
- Case key
- 170689
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-0765 73/3/30 HANOVER,MICH BEECH E35 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 43, 349 TIME - 1040 N3506B PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 114 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP BRIDGEPORT,CONN CHICAGO,ILL CLEVELAND,OHIO TYPE OF ACCIDENT PHASE OF OPERATION AIRFRAME FAILURE: IN FLIGHT IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE WEATHER - LOW CEILING WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 200 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/2 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 48 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 260 10 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE
Aircraft
- Registration
- N3506B
- Reported as
- Beech E35
- 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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.