ERA15CA317 · Ercoupe 415 C
Ercoupe 415 C · Accident: aerodynamic stall/spin on approach
From Fairmont Municipal Airport Frankman Field (4G7) to Fairmont Municipal Airport Frankman Field (4G7)
Event
- NTSB case
- ERA15CA317
- 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
- 0 · 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
Ercoupe 415 C
- Aircraft type
- Ercoupe 415
- 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
- N93606
- Operator
- Clem Robert J
- Onboard fatalities
- Unknown
- Route
- From Fairmont Municipal Airport Frankman Field (4G7), Fairmont, WVTo Fairmont Municipal Airport Frankman Field (4G7), Fairmont, WV
- Aircraft age
- About 69 years (built 1946)
- 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
- Approach
- 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
- Aerodynamic stall/spin
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, shortly after takeoff he noticed that there was no movement on the header tank fuel float gauge. He went on to say that the fuel float gauge then started to move "down quickly", and since he still had the airport insight, he decided to turn back and conduct a precautionary landing. As he approached for landing he "raised" the nose of the airplane to slow down; but became "too low and too slow" and the airplane collided with a road adjacent to the airport. The airplane sustained substantial damage to the fuselage and wings. Examination of the fuel float gauge by a Federal Aviation Administration inspector did not reveal any anomalies. In addition, the pilot reported there were no pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's failure to maintain airspeed and his exceedance of the wing's critical angle of attack, which resulted in an aerodynamic stall and subsequent collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15CA317
- Event ID
- 20150817X94448
- Case number
- ERA15CA317
- 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: a426d15031bd20097b14d4491517aafb50c6dda5590b1be08fea013ecb911401; retrieved 2026-09-16T02:40:57.332Z.