- Date
- August 10, 1969
- Place
- Suffolk, VA · SUFFOLK, VA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N9463YBeech N35
- Status
- Completed · report November 25, 1969
- Report
- Brief approved by the director
- Case key
- 164366
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-2482 69/8/10 SUFFOLK,VA BEECH N35 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 32, 150 TIME - 2055 N9463Y PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, ALL IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - SUFFOLK COUNTY DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP ORISKANY,NY SUFFOLK,VA NORFOLK,VA TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES LANDING: TRAFFIC PATTERN-CIRCLING PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER - LOW CEILING WEATHER - FOG WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 300 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG BELOW MINIMUMS TYPE OF FLIGHT PLAN SPECIAL VFR FIRE AFTER IMPACT REMARKS- STRUCK 60 FT TREES ON BASE LEG.
Aircraft
- Registration
- N9463Y
- Reported as
- Beech N35
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Suffolk County
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.