ERA14FA289 · Meyer Clair O 2/3 P 51B/C MUSTANG
Meyer Clair O 2/3 P 51B/C MUSTANG · Accident: loss of control in flight during initial climb
From Marion County Airport (MAO) to Marion County Airport (MAO)
Event
- NTSB case
- ERA14FA289
- 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
Meyer Clair O 2/3 P 51B/C MUSTANG
- Aircraft type
- Meyer Clair 2
- 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
- N51BM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marion County Airport (MAO), Marion, SCTo Marion County Airport (MAO), Marion, SC
- Aircraft age
- About 34 years (built 1980)
- 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
- Initial climb
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Physical
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The private pilot's wife reported that he planned to conduct taxi tests in the airplane on the day of the accident but that he did not intend to fly it. According to her recount of the accident, she observed the pilot taxi the airplane to the beginning of the runway where it idled for several minutes while the pilot waited for another airplane to depart. The pilot then initiated a takeoff roll and the airplane lifted off the ground about midfield with the landing gear retracted. As the airplane climbed, it "entered a sharp left turn," which was followed by a nose down dive. Another witness reported that he observed the pilot complete an engine run-up and then take off and enter a "shallow" climb. About 1,000 ft above the ground, the airplane entered a nose-down descent, and then impacted a corn field about 1 nautical mile from the airport.
Postaccident examination of the airframe did not reveal any anomalies that would have precluded normal operation. The engine did not display any evidence of lubrication distress or internal scoring indicative of an engine seizure or other catastrophic failure. Additionally, the witnesses reported no interruptions in engine power throughout the flight. Although these findings suggest that the airplane was under power, the investigation was unable to determine how much power the engine was producing at the time of the accident.
The pilot was issued a Federal Aviation Administration third-class medical certificate about 4 months before the accident. On his application for the certificate, he reported no significant medical conditions, no prescription medications, and no visits to other healthcare providers. Records obtained from his personal physician indicated that he had a history of diabetes, hypertension, high cholesterol, coronary artery disease, valvular disease, and cardiac arrhythmias. In addition, his medical history included hospital admissions for coronary artery bypass surgery, gallbladder removal, and quarterly visits for several years before the accident. The pilot had also been prescribed several prescription medications to control these conditions; only one of which, a sleep aid, was identified during postaccident toxicological testing. These findings indicate that the pilot was not compliant with his treatment regimen around the time of the accident.
The pilot's cardiovascular conditions and his failure to use the prescribed medications to treat them put him at high risk for a number of incapacitating symptoms that would not have been evident during the autopsy, including severe chest pain and shortness of breath from angina or a heart attack, sudden inability to use the arm and leg on one side (stroke), and sudden loss of consciousness from a hemorrhagic stroke or arrhythmia. It is likely that the pilot was incapacitated at the time of the accident due to his cardiovascular disease, which resulted in his loss of airplane control.
Probable cause
The airplane's impact with terrain shortly after takeoff due to a physiological incapacitation of the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14FA289
- Event ID
- 20140613X02343
- Case number
- ERA14FA289
- 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, coordinates. 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: 41c92b1ac2ee47d842f22b27d5cbbb257529b0423e6187ae68d6cbfd0f436541; retrieved 2026-09-14T17:19:29.181Z.