- Date
- October 24, 1976
- Place
- Chester, MT · CHESTER, MT
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6803SBeech A36
- Status
- Completed · report January 19, 1977
- Report
- Brief approved by the director
- FAA report
- 19761024039159A
- Case key
- 201362
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-3614 76/10/24 NR.CHESTER,MT BEECH A36 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 37, 646 TIME - 0132 N6803S PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 361 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION MINOT,ND SHELBY,MT 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 - FOG TERRAIN - HIGH OBSTRUCTIONS MISCELLANEOUS ACTS,CONDITIONS - ALTIMETER SETTING-INCORRECT WEATHER BRIEFING - BRIEFED BY WEATHER BUREAU PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/4 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 21 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 110 4 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR VFR REMARKS- RISING TERRAIN AND DARKNESS
Aircraft
- Registration
- N6803S
- Reported as
- Beech A36
- 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.