FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA138 · Beech F33 A

1 Mar 2014 · Lumberport, WV, United States

Beech F33 A · Accident en route

From Fairmont Municipal Airport Frankman Field (4G7) to Fairmont Municipal Airport Frankman Field (4G7)

Report a problem

Event

NTSB case
ERA14FA138
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
1 · all aircraft and ground
Ground fatalities
Unknown
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
Visual Meteorological Cond

Beech F33 A

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
N7203E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fairmont Municipal Airport Frankman Field (4G7), Fairmont, WVTo Fairmont Municipal Airport Frankman Field (4G7), Fairmont, WV
Aircraft age
About 30 years (built 1984)
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
Defining eventThe 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
Miscellaneous/other
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Physical

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot was conducting a local personal flight. Radar data indicated that the airplane took off from its home airport and flew westbound for about 23 minutes and then reversed course back toward the airport. Radar data indicated no major course deviations after the turn, but the data did indicate that the airplane's altitude deviated many times. Toward the end of the flight, the airplane started to descend, and the last two recorded altitudes indicated that the airplane reached a descent rate of 9,600 ft per minute. The airplane subsequently impacted a ridgeline, during which the airplane was highly fractured, with debris coming to rest on the downslope beyond the ridgeline. No preexisting mechanical anomalies were found that would have precluded normal operation, and propeller blade signatures were consistent with the engine producing power at the time of impact.

The pilot had a history of hypertension, depression, and anxiety and had experienced a stroke 6 years before the accident. His personal physician at that time, who was also a Federal Aviation Administration (FAA) designated aviation medical examiner (AME), prescribed multiple medications for these conditions during visits for personal medical care 5 and 6 years before the accident, including two medications the FAA considered disqualifying for use by pilots. Neither the pilot nor the AME reported these conditions or their treatment to the FAA when the pilot obtained aviation medical certificates 4 and 2 years before the accident. The AME only provided medical records up to 5 years before the accident.

The pilot's autopsy was limited by the degree of damage to his body. The local medical examiner identified mirtazapine and ethanol in the muscle, and subsequent testing at the FAA Civil Aerospace Medical Institute identified amlodipine, mirtazapine, and valsartan but no ethanol.

Mirtazapine is an antidepressant whose mechanism is unknown. Although the pilot had been diagnosed and treated for depression and anxiety, there were no available records describing the effectiveness of the treatment or the extent of the pilot's symptoms around the time of the accident. Although mirtazapine can be sedating, the pilot had apparently been using it for several years. The family reported that the pilot had planned to travel in the weeks following the accident, and there were no reports of new or increased stressors. The ethanol identified by the medical examiner likely resulted from postmortem production rather than ingestion and did not contribute to the accident. Amlodipine and valsartan are used to lower blood pressure, and although the pilot's hypertension and its treatment likely did not contribute directly to the accident, it increased his risk of recurrent stroke or other cardiovascular event.

There were no records provided nor any reports from the family about who prescribed the pilot's current medications or who might have been treating him in the 5 years before the accident if not his personal physician/AME. Current recommendations for treatment following strokes are designed to decrease the likelihood of a recurrent event. Guidelines include ongoing treatment with antiplatelet medications, such as aspirin or clopidogrel, evaluation and aggressive treatment of cholesterol, and careful management of hypertension and diabetes. However, there was no evidence from available records or the toxicology results indicating that the pilot was using antiplatelet medication or a cholesterol-lowering agent.

If the pilot and his AME had fully reported the pilot's medical conditions and medications to the FAA, additional testing, such as brain imaging and neuropsychiatric and neurocognitive testing, would have been required for FAA issuance of a medical certificate. Without further testing, the extent of any impairment from the pilot's illnesses or their treatment could not be determined. According to the available evidence, the pilot's stroke risks were inadequately treated and put him at a high risk for a recurrent stroke or a cardiovascular event. These risks likely led to the pilot's acute impairment or incapacitation, which resulted in his flight into terrain.

Probable cause

A stroke or cardiovascular event, which resulted in the pilot’s acute impairment or incapacitation and his subsequent flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA138
Event ID
20140301X53654
Case number
ERA14FA138
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: a9432b1c0ce883e9369223d6172c877d12f56328f4a7ca8fb569ddc2ec4615d1; retrieved 2026-09-14T16:11:20.096Z.