- Date
- February 2, 1969
- Place
- Afton, VA · AFTON, VA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N3871YCessna 210D
- Status
- Completed · report May 2, 1969
- Report
- Brief approved by the director
- Case key
- 191586
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-0158 69/2/2 AFTON,VA CESSNA 210D CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 42, 1018 TIME - 1500 N3871Y PX- 0 0 0 BUSINESS TOTAL HOURS, 118 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. 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 WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY RADIO WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 600 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 3 MILES OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 41 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 60 7 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE REMARKS- RECOVERY DATE-2/4/69.NOT INST RATED.STRUCK TOP OF MT RIDGE.
Aircraft
- Registration
- N3871Y
- Reported as
- Cessna 210D
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N3871YRegistration cancelled Dec 10, 2019 · Cessna 210DAirframe modelCessna 210DEngine modelContinental IO-520 series
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.