CEN10CA215 · Murray Starlite
Murray Starlite · Accident: system/component malfunction/failure (non-power) during landing
From Marion, IA to Shelby County Airport (2H0)
Event
- NTSB case
- CEN10CA215
- 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
Murray Starlite
- Aircraft type
- Murray STARLITE
- 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
- N4326D
- Operator
- Denis Boissonneault
- Onboard fatalities
- Unknown
- Route
- From Marion, IATo Shelby County Airport (2H0), Shelbyville, 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
- 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
- System/component malfunction/failure (non-power)
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that when the experimental, amateur-built airplane touched down for landing, the left main tire “locked up” and the airplane veered to the left. The pilot applied full right rudder and aileron, but the airplane continued to veer off the left side of the runway. The airplane sustained substantial damage when it entered a plowed field, which caused the main landing gear to collapse and the left main tire to go through the left wing. Postaccident inspection of the airplane revealed that left main landing gear rotor and brake exhibited rust with “pitting” and “scarring.” The left tire had a bald spot which was consistent with it being “locked up” and skidding. The aircraft logbook indicated that the airplane’s last conditional inspection was conducted on March 24, 2009, which was about 13 months prior to the accident. The accident flight was the first flight since the airplane had been stored for the winter in August 2009. The pilot reported that he “could have removed the wheels and checked them thoroughly” since the airplane had been in a "barn/hangar" over the winter.
Probable cause
The corrosion of the left landing gear rotor and brake, which resulted in the loss of directional control during the landing rollout, and the pilot's inadequate preflight inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA215
- Event ID
- 20100421X65546
- Case number
- CEN10CA215
- 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. 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: 581d1b6d2afb4520ed4cd892c26837d7c0ed00287805fe6b723cc0f13152c9ed; retrieved 2026-09-15T13:53:07.146Z.