Beechcraft F33A N6033U

Summary

On 10 June 1998 at about 23:40 local time, a Beechcraft F33A registered N6033U was involved in an accident near Delaplane, Virginia, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

10 June 1998 at 23:40

Classification

Accident

Location

Delaplane, Virginia, United States

Coordinates

38.9192, -77.9204

Aircraft

Beechcraft F33A

Registration

N6033U

Category

Airplane

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

North Wilkesbor → Frederick

Aircraft damage

Destroyed

Weather

IMC

Light

Day

NTSB number

IAD98FA068

2 people died.

The pilot's inadequate in-flight decision which led to VFR flight into instrument meteorological conditions. Also causal was the pilot's failure to maintain adequate terrain clearance resulting in collision with mountainous terrain. Contributing factors were low clouds, fog, mountainous terrain, obscuration, low altitude flying and the pilot's self-induced pressure.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The pilot and pilot rated passenger (PRP) were en route to Frederick (FDK), Maryland, when the airplane collided with mountainous terrain 40 miles from the destination. Several witnesses near the crash site heard an airplane overfly their homes at a low altitude. They reported that the engine was operating as it flew overhead, then they heard the engine stop followed by a 'thud.' According to the witnesses, it was cloudy, and the fog had covered the tops of the 50 foot tall trees. The flight followed the successful completion of a visual flight rules (VFR) cross country flying event. According to the Chairperson of the U.S. Air Race, Inc., the event organizers terminated the daylight and VFR-only event early because weather conditions did not appear to permit a VFR flight to FDK. Several VFR aircraft landed short of FDK and drove the remaining distance. According to Air Traffic Control records the pilot did not file a flight plan. An Air Traffic Controller said, '...Aircraft were canceling their [instrument flight rules] IFR either after landing or short final which caused other inbounds to hold or get delaying vectors.'. AIRMET SIERRA update number 5 issued at 1545, and was current for mountain obscuration and IFR ceilings and visibility's over the accident location. The weather at FDK was IFR and instrument approaches were in use. Examination of the airplane and engine did not disclose any evidence of mechanical malfunction.

Quoted verbatim from the NTSB record.