CHI02LA022 · Smith Aerostar 601
Smith Aerostar 601 · Accident: airframe, component or system failure during landing
From General Mitchell International Airport (MKE) to Vermilion Regional Airport (DNV)
Event
- NTSB case
- CHI02LA022
- 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
Smith Aerostar 601
- Aircraft type
- Smith AEROSTAR 601
- 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
- N128AC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From General Mitchell International Airport (MKE), Milwaukee, WITo Vermilion Regional Airport (DNV), Danville, IL
- 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
- Airframe, component or system failure
- 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
- Directional control › Not possible
- Landing gear, main gear strut scissors › Separation
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane veered off of the runway during landing. The pilot reported that during the landing, he heard a loud noise and then the airplane veered off of the runway. Upon inspection, the landing gear scissor assembly was found broken loose from the upper mounting collar on the landing gear strut and the lower strut was rotated about 90 degrees. A request was made that the broken parts be sent to the National Transportation Safety Board investigator for further examination. The parts were not received. No other anomalies were found with the airplane or its systems that could be associated with a pre-impact condition.
Probable cause
The separation of the main landing gear scissor assembly during landing for undetermined reasons, resulting in the directional control of the airplane not being possible.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA022
- Event ID
- 20011108X02215
- Case number
- CHI02LA022
- 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: 03826339d0ef2cb9c0279284aee10b7e0cd96726ffd97c6e3e09c93186418790; retrieved 2026-09-22T11:25:41.915Z.