IAD98FA068 · Beech F33A
Beech F33A · Accident: in flight encounter with weather en route
From Wilkes County Airport (UKF) to Frederick Municipal Airport (FDK)
Event
- NTSB case
- IAD98FA068
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Beech F33A
- Aircraft type
- Beechcraft 33
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N6033U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilkes County Airport (UKF), North Wilkesboro, NCTo Frederick Municipal Airport (FDK), Frederick, MD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98FA068
- Event ID
- 20001211X10329
- Case number
- IAD98FA068
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b4c36bcb1a1d8fd47cfffe058d6220ea4b216e863dd61865cb4a89970db47a9a; retrieved 2026-09-20T22:32:54.079Z.