CEN10CA191 · Maule M-5-210C
Maule M-5-210C · Accident: hard landing
From Flying Cloud Airport (KFCM) to Bismarck Municipal Airport (KBIS)
Event
- NTSB case
- CEN10CA191
- 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
Maule M-5-210C
- Aircraft type
- Maule M-5
- 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
- N62040
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flying Cloud Airport (KFCM), Eden Prairie, MNTo Bismarck Municipal Airport (KBIS), Bismarck, ND
- 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 · flare/touchdown
- 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
- Hard landing
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was attempting a crosswind landing on runway 31 in a tailwheel equipped airplane. He reported that the airplane began to sink during the landing flare, which resulted in a bounced landing. After the airplane touched down for the second time, the pilot pushed the control yoke forward, raising the tail, to ensure that the main landing gear stayed on the runway and to mitigate any potential for porpoising. He stated that his corrective actions were “not a very good move” with the crosswind condition, which resulted in reduced rudder effectiveness because the fuselage restricted airflow past the rudder control surface. The airplane veered off the left side of the runway, despite the pilot’s corrective inputs of right rudder and right brake. The airplane then ground-looped and struck a runway light. The right wing, right aileron and right elevator were substantially damaged. The pilot reported that there were no pre-impact mechanical malfunctions or failures that would have precluded normal operation of the airplane. He noted that the airplane was equipped with 26-inch diameter tires and single puck brakes. He suggested that with increased braking power, by the installation of dual puck brakes, his directional control would have been maintained. He also suggested that the use of another runway, better aligned with the wind, could have prevented the accident. A local weather station reported that the prevailing wind was out of the west-southwest between 10 and 15 knots.
Probable cause
The pilot’s failure compensate for the crosswinds resulting in a loss of directional control while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA191
- Event ID
- 20100405X70020
- Case number
- CEN10CA191
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-04-05.
- API snapshot SHA-256: ff11a2faaef83e8e46793d5bfb14ee3914e5d1ee44bb5c7d27f5c24d51e232b3; retrieved 2026-09-15T13:49:26.987Z.