CHI97LA057 · Beech 300
Beech 300 · Accident: overrun during landing
From Elkhart Municipal Airport (EKM) to Monroe County Airport (BMG)
Event
- NTSB case
- CHI97LA057
- 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
- 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 300
- Aircraft type
- Beechcraft 300
- 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
- N404EW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Elkhart Municipal Airport (EKM), Elkhart, INTo Monroe County Airport (BMG)
- 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
- Landing · landing roll
- 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
- Overrun
- 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
- Pilot in command › Distance/speed, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was flying his second ILS approach for runway 35 after performing a missed approach on his first ILS approach. The control tower reported 1/8 of a mile visibility in fog. The tower controller reported that the airplane was approximately 200-300 feet above the runway mid-field of the 6500-foot runway. The contract controller observed the airplane landing long and skidded off the end of the runway into the snow, collapsing the landing gear. There was interest by the pilot and his employer to land for a Indiana-Michigan basketball game. Weather minimums for the ILS 35 approach include 1/2 mile visibility.
Probable cause
the pilot's excessive distance/speed during the landing which led to his failure to attain a proper touchdown point on the runway. The factors involved were: the pilot's inadequate in-flight planning/decision, his failure proceed to the destination airport, pressure to land at the airport, and the weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA057
- Event ID
- 20001208X07271
- Case number
- CHI97LA057
- 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: eeff89d289f69a5d90fa58c9a0d209d8e83db0a4a1a233c412ddd927c4217c8c; retrieved 2026-09-22T20:28:01.559Z.