FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI91DEM01 · Ercoupe (Eng & Research Corp.) 415C

3 Nov 1990 · Shelby, MI, United States

Ercoupe (Eng & Research Corp.) 415C · Accident: loss of control in flight en route

From Muskegon County Airport (MKG) to Oceana County Airport (C04)

Report a problem

Event

NTSB case
CHI91DEM01
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
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

Ercoupe (Eng & Research Corp.) 415C

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
N9409B
Operator
Elmer N. Hall · private individual
Onboard fatalities
Unknown
Route
From Muskegon County Airport (MKG), Muskegon, MITo Oceana County Airport (C04), Shelby, MI
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
Loss of control in flight
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); Stall
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 › VFR flight into imc, continued

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

NTSB narrative

THE PRIVATE PILOT DEPARTED ON A SHORT VFR CROSS COUNTRY FLIGHT TO HIS HOME AIRPORT. THE AREA AROUND HIS HOME AIRPORT WAS FOGGED IN. VISIBILITY WAS ESTIMATED TO BE 3/4 OF A MILE WITH A CEILING VARYING FROM TREE TOP LEVEL TO 700 FEET ABOVE THE GROUND. WITNESSES REPORTED THAT THEY HEARD THE AIRPLANE FLYING AROUND THE AREA FOR 15 TO 30 MINUTES. THEY STATED IT WAS MAKING SOUNDS LIKE A 'CROP DUSTER'. TWO WITNESSES BRIEFLY SAW THE AIRPLANE COME OUT OF, AND RE-ENTER, THE LOW CLOUDS. THE AIRPLANE WAS OBSERVED COMING OUT OF THE CLOUDS, BANKING STEEPLY DURING A PULLUP MANEUVER AND STALLING. THE AIRPLANE ROLLED TO THE LEFT AND COLLIDED WITH THE GROUND AT A STEEP ANGLE.

Probable cause

THE PILOT'S CONTINUED FLIGHT INTO IMC.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI91DEM01
Event ID
20001212X24581
Case number
CHI91DEM01
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: 1ca2ad8e083d6cd7f33277c7fd62a4f9cc9b7f5c2ebef148cc79ac0015af7a04; retrieved 2026-09-21T02:05:51.397Z.